You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by Mark Struberg <st...@yahoo.de> on 2015/05/17 13:41:37 UTC

OWB 1.6.0 and tomee

Hi!

We did quite a bit of refactoring in OWB and I’ve now passed the CDI TCK with TomEE. I’ve pushed my changes to master.
We can now focus back on a few minor performance improvements and then go on and release OWB-1.6.0 for the upcoming TomEE-7.0.0 release.

LieGrue,
strub

Re: OWB 1.6.0 and tomee

Posted by Romain Manni-Bucau <rm...@gmail.com>.
https://issues.apache.org/jira/browse/TOMEE-731 is still working (ie no
regression for session replication :)). Great job Mark!

Updated arquillian.xml and cdi-tomee to ignore session serialization, if
you can give it a try please.


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com>

2015-05-17 14:20 GMT+02:00 Romain Manni-Bucau <rm...@gmail.com>:

>
> Le 17 mai 2015 14:16, "Mark Struberg" <st...@yahoo.de> a écrit :
> >
> > I did manually test it. But I’d be glad to have a more formal test or if
> someone else could verify those parts. We now solely rely on Tomcat
> clustering, so that should be pretty fine.
> >
>
> Same last time i checked using modjk, not sure how to test without heavily
> relying on the os/setup
>
> > Romain, if you manage to switch tomcat to not doing serialisation for
> the TCK.
> >
> > I know how to do it in the context xml (<Manager pathname=„“ />), but
> not quite sure how to do this just for the TCK runs.
> > If you can hack this then we can enable the two tests which I disabled
> with hindsight of CDITCK-482.
> >
>
> You can set a conf folder in arquillian.xml and put a server.xml inside
> this folder. Just set its path to arq conf property. Think we also have
> serverXml property for a direct path.
>
> Isnt ot enough?
>
> Currently at a cliff diving competition but will help tonight if still an
> issue.
>
> > LieGrue,
> > strub
> >
> > > Am 17.05.2015 um 14:09 schrieb Romain Manni-Bucau <
> rmannibucau@gmail.com>:
> > >
> > > Hi Mark
> > >
> > > Great to read
> > >
> > > Did you check clustering case? Several users rely on it in prod.
> > > Le 17 mai 2015 13:42, "Mark Struberg" <st...@yahoo.de> a écrit :
> > >
> > >> Hi!
> > >>
> > >> We did quite a bit of refactoring in OWB and I’ve now passed the CDI
> TCK
> > >> with TomEE. I’ve pushed my changes to master.
> > >> We can now focus back on a few minor performance improvements and
> then go
> > >> on and release OWB-1.6.0 for the upcoming TomEE-7.0.0 release.
> > >>
> > >> LieGrue,
> > >> strub
> >
>

Re: OWB 1.6.0 and tomee

Posted by Romain Manni-Bucau <rm...@gmail.com>.
Le 17 mai 2015 14:16, "Mark Struberg" <st...@yahoo.de> a écrit :
>
> I did manually test it. But I’d be glad to have a more formal test or if
someone else could verify those parts. We now solely rely on Tomcat
clustering, so that should be pretty fine.
>

Same last time i checked using modjk, not sure how to test without heavily
relying on the os/setup

> Romain, if you manage to switch tomcat to not doing serialisation for the
TCK.
>
> I know how to do it in the context xml (<Manager pathname=„“ />), but not
quite sure how to do this just for the TCK runs.
> If you can hack this then we can enable the two tests which I disabled
with hindsight of CDITCK-482.
>

You can set a conf folder in arquillian.xml and put a server.xml inside
this folder. Just set its path to arq conf property. Think we also have
serverXml property for a direct path.

Isnt ot enough?

Currently at a cliff diving competition but will help tonight if still an
issue.

> LieGrue,
> strub
>
> > Am 17.05.2015 um 14:09 schrieb Romain Manni-Bucau <rmannibucau@gmail.com
>:
> >
> > Hi Mark
> >
> > Great to read
> >
> > Did you check clustering case? Several users rely on it in prod.
> > Le 17 mai 2015 13:42, "Mark Struberg" <st...@yahoo.de> a écrit :
> >
> >> Hi!
> >>
> >> We did quite a bit of refactoring in OWB and I’ve now passed the CDI
TCK
> >> with TomEE. I’ve pushed my changes to master.
> >> We can now focus back on a few minor performance improvements and then
go
> >> on and release OWB-1.6.0 for the upcoming TomEE-7.0.0 release.
> >>
> >> LieGrue,
> >> strub
>

Re: OWB 1.6.0 and tomee

Posted by Mark Struberg <st...@yahoo.de>.
I did manually test it. But I’d be glad to have a more formal test or if someone else could verify those parts. We now solely rely on Tomcat clustering, so that should be pretty fine.

Romain, if you manage to switch tomcat to not doing serialisation for the TCK.

I know how to do it in the context xml (<Manager pathname=„“ />), but not quite sure how to do this just for the TCK runs.
If you can hack this then we can enable the two tests which I disabled with hindsight of CDITCK-482.

LieGrue,
strub

> Am 17.05.2015 um 14:09 schrieb Romain Manni-Bucau <rm...@gmail.com>:
> 
> Hi Mark
> 
> Great to read
> 
> Did you check clustering case? Several users rely on it in prod.
> Le 17 mai 2015 13:42, "Mark Struberg" <st...@yahoo.de> a écrit :
> 
>> Hi!
>> 
>> We did quite a bit of refactoring in OWB and I’ve now passed the CDI TCK
>> with TomEE. I’ve pushed my changes to master.
>> We can now focus back on a few minor performance improvements and then go
>> on and release OWB-1.6.0 for the upcoming TomEE-7.0.0 release.
>> 
>> LieGrue,
>> strub


Re: OWB 1.6.0 and tomee

Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hi Mark

Great to read

Did you check clustering case? Several users rely on it in prod.
 Le 17 mai 2015 13:42, "Mark Struberg" <st...@yahoo.de> a écrit :

> Hi!
>
> We did quite a bit of refactoring in OWB and I’ve now passed the CDI TCK
> with TomEE. I’ve pushed my changes to master.
> We can now focus back on a few minor performance improvements and then go
> on and release OWB-1.6.0 for the upcoming TomEE-7.0.0 release.
>
> LieGrue,
> strub