Re: Migration doc from TomEE 8.x to TomEE 9.x

[Alex The Rocker]

Hi François,

Just speaking from my own experience on a huge set of webapps to
migrate, but Eclipse Transformer was quite good for both source-level
& JAR (bytecode) level Java -> Jakarta EE migration. For sure, 80% of
the time was spent chasing the devil in details in the 20% remaining
glitches (mostly caused by deadly old code not even at EE8 level but
*older*, and fighting with some not quite supported old 3rd party
JARs..)

Alex




Le mer. 21 févr. 2024 à 12:17, COURTAULT Francois
 a écrit :
>
> THALES GROUP LIMITED DISTRIBUTION to email recipients
>
> Hello everyone,
>
> Is there any document somewhere which describes the way to migrate our 
> applications from TomEE 8.x to TomEE 9.x ?
> I saw that there is some tool available at Tomcat site like "Tomcat Migration 
> Tool for Jakarta EE 1.0.8 Released".
>
> Thanks in advance.
>
> Best regards.
>
>
>

Re: Health of this project -- should we keep going?

[Alex The Rocker]

Putting TomEE in attic would indeed be shame after all these years of
pretty good service.
Out of curiosity, how other open-sourced EE app servers are coping
with web services layer, if not using CXF ?

Thanks,
Alex

Le jeu. 12 oct. 2023 à 07:04, Benedict Eisenkrämer
 a écrit :
>
> Hi David,
>
> I think it would be a big loss if this project where to die, it is by
> far my favorite Applicationsserver.
> I am definitely willing to help further in the future, especially on the
> tck front.
>
> My main issue with tcks is, that we are very much reliant on other
> apache dependencies and therefore somewhat bound to their
> development-speed.
> For example, cxf has not yet released a JakartaEE 10 compatible version,
> meaning we can`t finish the tck, which is a bit frustrating.
>
> I am rather new to the project, but imho we should definitely keep going!
>
> Grüße Benedict
>
>
> On 11.10.23 21:36, David Blevins wrote:
> > Hi All,
> >
> > Wanted to share the state of this project as reported to the Apache board.
> >
> >   - https://tomee.apache.org/board-report-2023-09-20.txt
> >
> > The short version is we do not get enough help from you to keep this 
> > project going.
> >
> > Should we continue or should we just give up?
> >
> >
> >
> > -David
> >
>

Re: Is the new TomEE version 8.0.8 certified on JDK 17 ?

[Alex The Rocker]

Good question!

I have myself ran some tests with JDK 16, found a few glitches
(already tracked by some JIRAs), but no blockers.

I haven't yet started with JDK17 (waiting for my favorite OpenJ9-based
Java version to deliver JDK17 level, which soon take place soon).

Anyway the question of certifying TomEE with this new LTS (Long Term
Support) version of Java must be raised - I don't see how it could not
be the case.

Alex

Le mer. 15 sept. 2021 à 08:35, COURTAULT Francois
 a écrit :
>
> Hello,
>
> The question I want to ask is in the email Subject.
>
> Best Regards.
>
>
>

Re: New committer Cesar Hernandez

[Alex The Rocker]

Welcome Cesar!

Alexandre

Le jeu. 5 sept. 2019 à 09:56, COURTAULT Francois
 a écrit :
>
> Congratulation Cesar !
>
> -Original Message-
> From: Jean-Louis Monteiro [mailto:jlmonte...@tomitribe.com]
> Sent: jeudi 5 septembre 2019 09:53
> To: d...@tomee.apache.org; users@tomee.apache.org
> Subject: New committer Cesar Hernandez
>
> The Project Management Committee (PMC) for Apache TomEE has invited Cesar to 
> become a committer and we are pleased to announce that he has accepted.
>
> Cesar started contributing about a year ago.
> Aside from examples, he contributed a lot on the documentation which is 
> always something to improve especially in the open source world.
>
> When I started 10 years ago, a good friend of mine told me that in open 
> source projects, it's 50% contributor's responsibility to do well, and 50% 
> our responsibility committers and PMC to make sure they can.
>
> I must say Cesar over performed in this area. In the last 6 months he has 
> been the most active contributor on the mailing list. He also reviewed a 
> large amount of PRs and he's been key to help new contributors contribute.
>
> We all think he deserves becoming a TomEE committer and we are glad he 
> accepted.
>
> Being a committer enables easier contribution to the project since there is 
> no need to go via the patch submission process. This should enable better 
> productivity. Being a PMC member enables assistance with the management and 
> to guide the direction of the project.
>
>
> Please join me and send him a warm welcome and thank you.
> --
> Jean-Louis Monteiro
> https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftwitter.com%2Fjlouismonteirodata=02%7C01%7CFrancois.COURTAULT%40gemalto.com%7C21b5999a36ff4183319808d731d62575%7C37d0a9db7c464096bfe31add5b495d6d%7C0%7C0%7C637032668130941738sdata=9d4hsY4uUESwbsDlab4vsK3GKy%2Feem82rokemgjbNnc%3Dreserved=0
> https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.tomitribe.comdata=02%7C01%7CFrancois.COURTAULT%40gemalto.com%7C21b5999a36ff4183319808d731d62575%7C37d0a9db7c464096bfe31add5b495d6d%7C0%7C0%7C637032668130941738sdata=ObkAw%2Fyw4M8SM3h5JZAX9iLe7hyyyA%2F2dUcdi9lsOBc%3Dreserved=0
> 
>  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.

Re: Why jackson and jonhzon shipped with latest TomEE?

[Alex The Rocker]

Hello,

I agree with dkwakkel, Apache Johnzon should be enought for all TomEE
runtime requirements.Mixing two different JSON processors in same
classpath can lead to a dependency mess.

After all, ActiveMQ is an Apache project, and even if when it was
developed Apache Johnzon wasn't available, it would make great sense
to replace FasterXML Jackson (which isn't an Apache project, even if
it has Apache License 2.0) by Apache Johnzon.

How about a JIRA request on ActiveMQ for this "small" change ? :)

Kind regards,
Alex

Le mer. 19 juin 2019 à 12:22, Jonathan Gallimore
 a écrit :
>
> I think ActiveMQ pulls jackson in, as it uses Jackson internally. I don't
> know that we could avoid that without forking and making some (potentially
> big) changes.
>
> Jon
>
> On Wed, Jun 19, 2019 at 9:36 AM dkwakkel  wrote:
>
> > I see both jackson and johnzon are now part of TomEE 8 M2:
> > jackson-annotations-2.9.0.jar
> > jackson-core-2.9.4.jar
> > jackson-databind-2.9.4.jar
> > jackson-dataformat-yaml-2.9.4.jar
> > johnzon-core-1.1.11.jar
> > johnzon-jaxrs-1.1.11.jar
> > johnzon-jsonb-1.1.11.jar
> > johnzon-mapper-1.1.11.jar
> >
> > Should not only johnzon be enough?
> >
> >
> >
> > --
> > Sent from:
> > http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html
> >

Re: How can we use a Johnzon version more recent than TomEE’s, delivered in our WARs, to run JAX-RS services ?”

[Alex The Rocker]

Romain,

All we did was to build a 1.0.0-SNAPSHOT using JOHNZON-101 bugfix
found at  
https://git-wip-us.apache.org/repos/asf?p=johnzon.git;a=commit;h=d7b768fe10f6163be58ec3d4905c404ee9ce2f30

We found no other need of changes to vanilla Johnzon 1.0.0.

Out of curiosity : Johnzon 1.1.x has been available for a while: is it
considered for a TomEE 7.0.x future release, or only for TomEE 8.x ?

Best regards,
Alexandre


2017-12-01 22:59 GMT+01:00 Romain Manni-Bucau <rmannibu...@gmail.com>:
> Yes
>
> Is johnzon snapshot working for you or do you need some backports?
>
>
> Le 1 déc. 2017 21:48, "Alex The Rocker" <alex.m3...@gmail.com> a écrit :
>
>> Hello Romain,
>>
>> Thanks for your answer, I created:
>>
>> https://issues.apache.org/jira/browse/TOMEE-2153
>>
>> for asking the dependency upgrade of Johnzon in TomEE, and:
>>
>> https://issues.apache.org/jira/browse/JOHNZON-149
>>
>> for asking the release of Johnzon 1.0.1
>>
>> I hope this is the right way.
>>
>> Best regards,
>> Alexandre
>>
>>
>> 2017-12-01 13:52 GMT+01:00 Romain Manni-Bucau <rmannibu...@gmail.com>:
>> > Hi,
>> >
>> > 2017-12-01 13:17 GMT+01:00 Alex The Rocker <alex.m3...@gmail.com>:
>> >> Hi Romain,
>> >>
>> >> Thanks, I will give it a try.
>> >>
>> >> Back to TomEE+ 7.0.5 : should I fill a JIRA to ask upgrade of Johnzon
>> >> dependency from 1.0.0 to 1.0.1 (or to any version that fixes
>> >> JOHNZON-101) ?
>> >
>> > you can be johnzon should release a 1.0.1 before tomee tackles it - so
>> > probably a ticket on johnzon too.
>> >
>> >>
>> >> Best regards,
>> >>
>> >>
>> >> 2017-11-30 7:50 GMT+01:00 Romain Manni-Bucau <rmannibu...@gmail.com>:
>> >>> openejb.classloader.forced-load=org.apache.johnzon can be a good try
>> >>> but the API can't be changed for sure
>> >>>
>> >>> Romain Manni-Bucau
>> >>> @rmannibucau |  Blog | Old Blog | Github | LinkedIn
>> >>>
>> >>>
>> >>> 2017-11-30 7:48 GMT+01:00 Paul Carter-Brown <
>> paul.carter-br...@smilecoms.com>:
>> >>>> Hi Alex
>> >>>>
>> >>>> I don't think it will be possible to get the system classloader to use
>> >>>> johnzon in a war.
>> >>>>
>> >>>> Not ideal for you but here are some options:
>> >>>>
>> >>>> Include a .bat and .sh to the installer which they must run to
>> install your
>> >>>> war. This script can extract your johnzon jars into tomee/lib and then
>> >>>> install the war.
>> >>>>
>> >>>> Alternatively distribute your app as a docker image with everything
>> >>>> perfectly set up and ready to run. I guess this option depends on
>> whether
>> >>>> your war is one of many to be deployed to tomee.
>> >>>>
>> >>>> Paul
>> >>>>
>> >>>> Paul
>> >>>>
>> >>>> Sent from my phone. Message may be brief and contain typos.
>> >>>>
>> >>>>
>> >>>> On 30 Nov 2017 01:12, "Alex The Rocker" <alex.m3...@gmail.com> wrote:
>> >>>>
>> >>>>> Hello Paul,
>> >>>>>
>> >>>>> I am in a situation where I am not redistributing TomEE+, but only a
>> >>>>> WAR file, into which I plan to include latest version of Apache
>> >>>>> Johnzon jar files.
>> >>>>>
>> >>>>> So my question is really : will TomEE+ use by default the Apache
>> >>>>> Johnzon .jar file found in my WAR instead of the ones it has in its
>> >>>>> tomee/lib directory, or do I need to instruct the people who will
>> >>>>> install my WAR file to modify some Tomee+ configuration files in
>> order
>> >>>>> to instruct TomEE to load my WAR's jars instead of its jars?
>> >>>>>
>> >>>>> Best regards,
>> >>>>> Alexandre
>> >>>>>
>> >>>>>
>> >>>>> 2017-11-29 13:08 GMT+01:00 Paul Carter-Brown
>> >>>>> <paul.carter-br...@opposablethumbs.io>:
>> >>>>> > The 3 Johnzon jars sit in tomee/lib/ directory. You can delete the
>> old
>> >>>>> ones
>> >>>>> > and copy in the new ones built from source. Works for me.
>> >>>>> >
>> >>>>> > On Wed, Nov 29, 2017 at 1:32 PM, Alex The Rocker <
>> alex.m3...@gmail.com>
>> >>>>> > wrote:
>> >>>>> >
>> >>>>> >> Hello,
>> >>>>> >>
>> >>>>> >> While upgrading one of our webapp from TomEE+ 1.7 to TomEE+ 7, we
>> hit
>> >>>>> >> a regression on JAX-RS.
>> >>>>> >>
>> >>>>> >> After analysis, we found that we've been impacted by the same
>> issue as
>> >>>>> >> the one fixed in this JIRA:
>> >>>>> >> https://issues.apache.org/jira/browse/JOHNZON-101
>> >>>>> >>
>> >>>>> >> We would like anyway to move to TomEE+ 7.0.4, but without waiting
>> for
>> >>>>> >> a future TomEE+ 7.x that would include this Johnzon fix.
>> >>>>> >>
>> >>>>> >> We tried to package a more recent version of Johnzon into our web
>> app,
>> >>>>> >> but it seems that it wasn't take into account by TomEE's JAX-RS
>> >>>>> >> engine.
>> >>>>> >>
>> >>>>> >> What is the right way to get TomEE+ use the more recent  Johnzon
>> JARs
>> >>>>> >> when it's packaged in a WAR ?
>> >>>>> >>
>> >>>>> >> Best regards,
>> >>>>> >> Alex
>> >>>>> >>
>> >>>>>
>> >>>>
>> >>>> --
>> >>>>
>> >>>>
>> >>>> This email is subject to the disclaimer of Smile Communications at
>> http://www.smilecoms.com/home/email-disclaimer/ <http://www.smilecoms.com/
>> disclaimer>
>> >>>>
>>

Re: How can we use a Johnzon version more recent than TomEE’s, delivered in our WARs, to run JAX-RS services ?”

[Alex The Rocker]

Hello Romain,

Thanks for your answer, I created:

https://issues.apache.org/jira/browse/TOMEE-2153

for asking the dependency upgrade of Johnzon in TomEE, and:

https://issues.apache.org/jira/browse/JOHNZON-149

for asking the release of Johnzon 1.0.1

I hope this is the right way.

Best regards,
Alexandre


2017-12-01 13:52 GMT+01:00 Romain Manni-Bucau <rmannibu...@gmail.com>:
> Hi,
>
> 2017-12-01 13:17 GMT+01:00 Alex The Rocker <alex.m3...@gmail.com>:
>> Hi Romain,
>>
>> Thanks, I will give it a try.
>>
>> Back to TomEE+ 7.0.5 : should I fill a JIRA to ask upgrade of Johnzon
>> dependency from 1.0.0 to 1.0.1 (or to any version that fixes
>> JOHNZON-101) ?
>
> you can be johnzon should release a 1.0.1 before tomee tackles it - so
> probably a ticket on johnzon too.
>
>>
>> Best regards,
>>
>>
>> 2017-11-30 7:50 GMT+01:00 Romain Manni-Bucau <rmannibu...@gmail.com>:
>>> openejb.classloader.forced-load=org.apache.johnzon can be a good try
>>> but the API can't be changed for sure
>>>
>>> Romain Manni-Bucau
>>> @rmannibucau |  Blog | Old Blog | Github | LinkedIn
>>>
>>>
>>> 2017-11-30 7:48 GMT+01:00 Paul Carter-Brown 
>>> <paul.carter-br...@smilecoms.com>:
>>>> Hi Alex
>>>>
>>>> I don't think it will be possible to get the system classloader to use
>>>> johnzon in a war.
>>>>
>>>> Not ideal for you but here are some options:
>>>>
>>>> Include a .bat and .sh to the installer which they must run to install your
>>>> war. This script can extract your johnzon jars into tomee/lib and then
>>>> install the war.
>>>>
>>>> Alternatively distribute your app as a docker image with everything
>>>> perfectly set up and ready to run. I guess this option depends on whether
>>>> your war is one of many to be deployed to tomee.
>>>>
>>>> Paul
>>>>
>>>> Paul
>>>>
>>>> Sent from my phone. Message may be brief and contain typos.
>>>>
>>>>
>>>> On 30 Nov 2017 01:12, "Alex The Rocker" <alex.m3...@gmail.com> wrote:
>>>>
>>>>> Hello Paul,
>>>>>
>>>>> I am in a situation where I am not redistributing TomEE+, but only a
>>>>> WAR file, into which I plan to include latest version of Apache
>>>>> Johnzon jar files.
>>>>>
>>>>> So my question is really : will TomEE+ use by default the Apache
>>>>> Johnzon .jar file found in my WAR instead of the ones it has in its
>>>>> tomee/lib directory, or do I need to instruct the people who will
>>>>> install my WAR file to modify some Tomee+ configuration files in order
>>>>> to instruct TomEE to load my WAR's jars instead of its jars?
>>>>>
>>>>> Best regards,
>>>>> Alexandre
>>>>>
>>>>>
>>>>> 2017-11-29 13:08 GMT+01:00 Paul Carter-Brown
>>>>> <paul.carter-br...@opposablethumbs.io>:
>>>>> > The 3 Johnzon jars sit in tomee/lib/ directory. You can delete the old
>>>>> ones
>>>>> > and copy in the new ones built from source. Works for me.
>>>>> >
>>>>> > On Wed, Nov 29, 2017 at 1:32 PM, Alex The Rocker <alex.m3...@gmail.com>
>>>>> > wrote:
>>>>> >
>>>>> >> Hello,
>>>>> >>
>>>>> >> While upgrading one of our webapp from TomEE+ 1.7 to TomEE+ 7, we hit
>>>>> >> a regression on JAX-RS.
>>>>> >>
>>>>> >> After analysis, we found that we've been impacted by the same issue as
>>>>> >> the one fixed in this JIRA:
>>>>> >> https://issues.apache.org/jira/browse/JOHNZON-101
>>>>> >>
>>>>> >> We would like anyway to move to TomEE+ 7.0.4, but without waiting for
>>>>> >> a future TomEE+ 7.x that would include this Johnzon fix.
>>>>> >>
>>>>> >> We tried to package a more recent version of Johnzon into our web app,
>>>>> >> but it seems that it wasn't take into account by TomEE's JAX-RS
>>>>> >> engine.
>>>>> >>
>>>>> >> What is the right way to get TomEE+ use the more recent  Johnzon JARs
>>>>> >> when it's packaged in a WAR ?
>>>>> >>
>>>>> >> Best regards,
>>>>> >> Alex
>>>>> >>
>>>>>
>>>>
>>>> --
>>>>
>>>>
>>>> This email is subject to the disclaimer of Smile Communications at 
>>>> http://www.smilecoms.com/home/email-disclaimer/ 
>>>> <http://www.smilecoms.com/disclaimer>
>>>>

Re: How can we use a Johnzon version more recent than TomEE’s, delivered in our WARs, to run JAX-RS services ?”

[Alex The Rocker]

Hi Romain,

Thanks, I will give it a try.

Back to TomEE+ 7.0.5 : should I fill a JIRA to ask upgrade of Johnzon
dependency from 1.0.0 to 1.0.1 (or to any version that fixes
JOHNZON-101) ?

Best regards,


2017-11-30 7:50 GMT+01:00 Romain Manni-Bucau <rmannibu...@gmail.com>:
> openejb.classloader.forced-load=org.apache.johnzon can be a good try
> but the API can't be changed for sure
>
> Romain Manni-Bucau
> @rmannibucau |  Blog | Old Blog | Github | LinkedIn
>
>
> 2017-11-30 7:48 GMT+01:00 Paul Carter-Brown <paul.carter-br...@smilecoms.com>:
>> Hi Alex
>>
>> I don't think it will be possible to get the system classloader to use
>> johnzon in a war.
>>
>> Not ideal for you but here are some options:
>>
>> Include a .bat and .sh to the installer which they must run to install your
>> war. This script can extract your johnzon jars into tomee/lib and then
>> install the war.
>>
>> Alternatively distribute your app as a docker image with everything
>> perfectly set up and ready to run. I guess this option depends on whether
>> your war is one of many to be deployed to tomee.
>>
>> Paul
>>
>> Paul
>>
>> Sent from my phone. Message may be brief and contain typos.
>>
>>
>> On 30 Nov 2017 01:12, "Alex The Rocker" <alex.m3...@gmail.com> wrote:
>>
>>> Hello Paul,
>>>
>>> I am in a situation where I am not redistributing TomEE+, but only a
>>> WAR file, into which I plan to include latest version of Apache
>>> Johnzon jar files.
>>>
>>> So my question is really : will TomEE+ use by default the Apache
>>> Johnzon .jar file found in my WAR instead of the ones it has in its
>>> tomee/lib directory, or do I need to instruct the people who will
>>> install my WAR file to modify some Tomee+ configuration files in order
>>> to instruct TomEE to load my WAR's jars instead of its jars?
>>>
>>> Best regards,
>>> Alexandre
>>>
>>>
>>> 2017-11-29 13:08 GMT+01:00 Paul Carter-Brown
>>> <paul.carter-br...@opposablethumbs.io>:
>>> > The 3 Johnzon jars sit in tomee/lib/ directory. You can delete the old
>>> ones
>>> > and copy in the new ones built from source. Works for me.
>>> >
>>> > On Wed, Nov 29, 2017 at 1:32 PM, Alex The Rocker <alex.m3...@gmail.com>
>>> > wrote:
>>> >
>>> >> Hello,
>>> >>
>>> >> While upgrading one of our webapp from TomEE+ 1.7 to TomEE+ 7, we hit
>>> >> a regression on JAX-RS.
>>> >>
>>> >> After analysis, we found that we've been impacted by the same issue as
>>> >> the one fixed in this JIRA:
>>> >> https://issues.apache.org/jira/browse/JOHNZON-101
>>> >>
>>> >> We would like anyway to move to TomEE+ 7.0.4, but without waiting for
>>> >> a future TomEE+ 7.x that would include this Johnzon fix.
>>> >>
>>> >> We tried to package a more recent version of Johnzon into our web app,
>>> >> but it seems that it wasn't take into account by TomEE's JAX-RS
>>> >> engine.
>>> >>
>>> >> What is the right way to get TomEE+ use the more recent  Johnzon JARs
>>> >> when it's packaged in a WAR ?
>>> >>
>>> >> Best regards,
>>> >> Alex
>>> >>
>>>
>>
>> --
>>
>>
>> This email is subject to the disclaimer of Smile Communications at 
>> http://www.smilecoms.com/home/email-disclaimer/ 
>> <http://www.smilecoms.com/disclaimer>
>>

Re: How can we use a Johnzon version more recent than TomEE’s, delivered in our WARs, to run JAX-RS services ?”

[Alex The Rocker]

Hello Romain,

I have read the page you linked, but I'm afraid it's unrelated to my
need : I do not want to change TomEE+ 7.0.4's javaee-api jar, but only
to find a way to instruct TomEE+ 7.0.4 to use Apache Johnzon 1.1.4 jar
files which I'm going to include into my application's WAR file.

My fear is that TomEE+ 7.0.4 will attempt to use its own old version
of Apache Johnzon 1.0.0 instead of the newer one of my web app when
executing my JAX-RS web services.

Is this the case or not?

Other (somehow related) question : will TomEE+ 7.0.5 include a newer
Apache Johnzon version fixing this JIRA
https://issues.apache.org/jira/browse/JOHNZON-101 ?

Best regards,
Alexandre


2017-11-29 13:27 GMT+01:00 Romain Manni-Bucau <rmannibu...@gmail.com>:
> This trick can be used for johnzon
> https://rmannibucau.wordpress.com/2013/07/19/little-tip-to-help-you-to-test-javaee-7-in-tomee-with-tomee-maven-plugin/
>
> side note: don't forget to upgrade jsonp and jsonb api jar as well.
>
> Romain Manni-Bucau
> @rmannibucau |  Blog | Old Blog | Github | LinkedIn
>
>
> 2017-11-29 13:08 GMT+01:00 Paul Carter-Brown
> <paul.carter-br...@opposablethumbs.io>:
>> The 3 Johnzon jars sit in tomee/lib/ directory. You can delete the old ones
>> and copy in the new ones built from source. Works for me.
>>
>> On Wed, Nov 29, 2017 at 1:32 PM, Alex The Rocker <alex.m3...@gmail.com>
>> wrote:
>>
>>> Hello,
>>>
>>> While upgrading one of our webapp from TomEE+ 1.7 to TomEE+ 7, we hit
>>> a regression on JAX-RS.
>>>
>>> After analysis, we found that we've been impacted by the same issue as
>>> the one fixed in this JIRA:
>>> https://issues.apache.org/jira/browse/JOHNZON-101
>>>
>>> We would like anyway to move to TomEE+ 7.0.4, but without waiting for
>>> a future TomEE+ 7.x that would include this Johnzon fix.
>>>
>>> We tried to package a more recent version of Johnzon into our web app,
>>> but it seems that it wasn't take into account by TomEE's JAX-RS
>>> engine.
>>>
>>> What is the right way to get TomEE+ use the more recent  Johnzon JARs
>>> when it's packaged in a WAR ?
>>>
>>> Best regards,
>>> Alex
>>>

Re: How can we use a Johnzon version more recent than TomEE’s, delivered in our WARs, to run JAX-RS services ?”

[Alex The Rocker]

Hello Paul,

I am in a situation where I am not redistributing TomEE+, but only a
WAR file, into which I plan to include latest version of Apache
Johnzon jar files.

So my question is really : will TomEE+ use by default the Apache
Johnzon .jar file found in my WAR instead of the ones it has in its
tomee/lib directory, or do I need to instruct the people who will
install my WAR file to modify some Tomee+ configuration files in order
to instruct TomEE to load my WAR's jars instead of its jars?

Best regards,
Alexandre


2017-11-29 13:08 GMT+01:00 Paul Carter-Brown
<paul.carter-br...@opposablethumbs.io>:
> The 3 Johnzon jars sit in tomee/lib/ directory. You can delete the old ones
> and copy in the new ones built from source. Works for me.
>
> On Wed, Nov 29, 2017 at 1:32 PM, Alex The Rocker <alex.m3...@gmail.com>
> wrote:
>
>> Hello,
>>
>> While upgrading one of our webapp from TomEE+ 1.7 to TomEE+ 7, we hit
>> a regression on JAX-RS.
>>
>> After analysis, we found that we've been impacted by the same issue as
>> the one fixed in this JIRA:
>> https://issues.apache.org/jira/browse/JOHNZON-101
>>
>> We would like anyway to move to TomEE+ 7.0.4, but without waiting for
>> a future TomEE+ 7.x that would include this Johnzon fix.
>>
>> We tried to package a more recent version of Johnzon into our web app,
>> but it seems that it wasn't take into account by TomEE's JAX-RS
>> engine.
>>
>> What is the right way to get TomEE+ use the more recent  Johnzon JARs
>> when it's packaged in a WAR ?
>>
>> Best regards,
>> Alex
>>

How can we use a Johnzon version more recent than TomEE’s, delivered in our WARs, to run JAX-RS services ?”

[Alex The Rocker]

Hello,

While upgrading one of our webapp from TomEE+ 1.7 to TomEE+ 7, we hit
a regression on JAX-RS.

After analysis, we found that we've been impacted by the same issue as
the one fixed in this JIRA:
https://issues.apache.org/jira/browse/JOHNZON-101

We would like anyway to move to TomEE+ 7.0.4, but without waiting for
a future TomEE+ 7.x that would include this Johnzon fix.

We tried to package a more recent version of Johnzon into our web app,
but it seems that it wasn't take into account by TomEE's JAX-RS
engine.

What is the right way to get TomEE+ use the more recent  Johnzon JARs
when it's packaged in a WAR ?

Best regards,
Alex

Re: Specifying org.apache.johnzon.max-string-length for a given TomEE+ instance

[Alex The Rocker]

Great, thanks!

2017-10-07 16:36 GMT+02:00 Romain Manni-Bucau <rmannibu...@gmail.com>:
> yes in CATALINA_OPTS
>
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> <https://rmannibucau.metawerx.net/> | Old Blog
> <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau>
>
> 2017-10-07 15:56 GMT+02:00 Alex The Rocker <alex.m3...@gmail.com>:
>
>> Hi Romain,
>>
>> Thanks, and could this property be set using setenv.sh ?
>>
>> Best regards,
>> Alexandre
>>
>> 2017-10-06 23:17 GMT+02:00 Romain Manni-Bucau <rmannibu...@gmail.com>:
>> > Hi
>> >
>> > You can set it in conf/system.properties of the instance (base) yes
>> >
>> > Le 6 oct. 2017 21:57, "Alex The Rocker" <alex.m3...@gmail.com> a écrit :
>> >
>> >> Hello,
>> >>
>> >> Some of our apps fail to work with default value of
>> >> org.apache.johnzon.max-string-length setting (8KB).
>> >>
>> >> But most of our apps are happy with this settings' default value.
>> >>
>> >> Thus, I don't want to change this default value in TomEE+ install
>> >> directory.
>> >> Would it be possible to overlead this
>> >> org.apache.johnzon.max-string-length property for a TomEE+ instance
>> >> pointing to a TomEE+ installation where this property is kept at its
>> >> default value?
>> >>
>> >> If yes then how?
>> >>
>> >> Best regards,
>> >> Alexandre
>> >>
>>

Re: Specifying org.apache.johnzon.max-string-length for a given TomEE+ instance

[Alex The Rocker]

Hi Romain,

Thanks, and could this property be set using setenv.sh ?

Best regards,
Alexandre

2017-10-06 23:17 GMT+02:00 Romain Manni-Bucau <rmannibu...@gmail.com>:
> Hi
>
> You can set it in conf/system.properties of the instance (base) yes
>
> Le 6 oct. 2017 21:57, "Alex The Rocker" <alex.m3...@gmail.com> a écrit :
>
>> Hello,
>>
>> Some of our apps fail to work with default value of
>> org.apache.johnzon.max-string-length setting (8KB).
>>
>> But most of our apps are happy with this settings' default value.
>>
>> Thus, I don't want to change this default value in TomEE+ install
>> directory.
>> Would it be possible to overlead this
>> org.apache.johnzon.max-string-length property for a TomEE+ instance
>> pointing to a TomEE+ installation where this property is kept at its
>> default value?
>>
>> If yes then how?
>>
>> Best regards,
>> Alexandre
>>

Specifying org.apache.johnzon.max-string-length for a given TomEE+ instance

[Alex The Rocker]

Hello,

Some of our apps fail to work with default value of
org.apache.johnzon.max-string-length setting (8KB).

But most of our apps are happy with this settings' default value.

Thus, I don't want to change this default value in TomEE+ install directory.
Would it be possible to overlead this
org.apache.johnzon.max-string-length property for a TomEE+ instance
pointing to a TomEE+ installation where this property is kept at its
default value?

If yes then how?

Best regards,
Alexandre

Re: Tomcat security issues and tomee 1.7.x

[Alex The Rocker]

Hello,

Thank you very much for this initiative.

I'm getting ready to test TomEE+ 1.7.5 release candidate artifacts as
soon as they'll be available.

I've got some complex web apps that usually prove to be a good torture test ;)

Best regards,
@lex

2017-04-14 0:19 GMT+02:00 Mark Struberg :
> +1 John, txs for jumping in!
>
> I'll be around if you need an additional pair of eyes.
>
> LieGrue,
> strub
>
>> Am 13.04.2017 um 16:45 schrieb Jonathan Gallimore :
>>
>> Thanks for your mail! I think we're probably due a 1.7.x release by now. If
>> there's no objections, I'm happy to volunteer to be the release manager and
>> get that underway.
>>
>> Jon
>>
>> On Thu, Apr 13, 2017 at 2:12 PM, Kirys  wrote:
>>
>>> Hi all
>>>
>>> Knowiing the latest security issues of tomcat 7, is there any plan of
>>> release another version of tomee 1.7 with updated tomcat?
>>>
>>> Bye
>>>
>>> K.
>>>
>>>
>>
>>
>> --
>> Jonathan Gallimore
>> http://twitter.com/jongallimore
>> http://www.tomitribe.com
>

Missing TomEE 1.6.0 announce at http://tomee.apache.org/index.html ?

[Alex The Rocker]

Hi,

I'm wondering why almost 3 weeks after TomEE 1.6.0 final made it way (great
thanks for this of course), it's still not announced on TomEE's front page:
http://tomee.apache.org/index.html.

You TomEE people should be proud of this release, casual visitors might
have the impression that TomEE's still felt asleep with version 1.5.2
announced 23th of April 2013.

More generally speaking, this Latest news list isn't making justice to
the huge flow of exchanges on users  dev lists, which lots of solutions
found.

Yes, that's PR, but you know what? this word is trapped with first
impression behaviors...

Thanks,
Alex.

Re: Getting spammed a guru

[Alex The Rocker]

Got spammed too :(



On Wed, Nov 13, 2013 at 2:33 PM, James Green james.mk.gr...@gmail.comwrote:

 So I just got an email from Apache TomEE Support claiming to offer
 professional support with a 20% discount. The from address is a
 yahoo.comaccount allegedly owned by Java EE Guru Gurkan Erdogdu.

 I have no idea how he or his organisation have my address but apparently
 I've shown an interest in the product and I can manage my mailing list
 preferences.

 Posting here slightly alarmed in case someone is monitoring this list and
 adding address found. I'm willing to be proven wrong of course. Any others
 receiving such emails?

 Thanks,

 James

Re: Blocking issue with TomEE1.6.0+Snapshot221: can't start because REST parent abstract class instanciation error

[Alex The Rocker]

Romain:

Good news, the TomEE+ package at
http://people.apache.org/~rmannibucau/apache-tomee-plus-1.6.0-SNAPSHOT.zipfixed
your web app blocking issue (we ran full non-reg tests automated +
manual QA tests).

Is this fix already part of lasted Snapshot?
Can we be sure that this fix will be available in 1.6.0 final ?

Best regards,
Alex



On Wed, Nov 6, 2013 at 6:21 PM, Alex The Rocker alex.m3...@gmail.comwrote:

 Romain:

 First tests are positive (and the sample is now OK) ; but to be 100% sure
 I have delivered this fix version into our automated test system for a full
 nightly replay of our test cases. Tomorrow I'll have the final word on this.

 Thanks (a lot),

 Alex.



 On Wed, Nov 6, 2013 at 3:07 PM, Romain Manni-Bucau 
 rmannibu...@gmail.comwrote:

 here is a tomee
 http://people.apache.org/~rmannibucau/apache-tomee-plus-1.6.0-SNAPSHOT.zip
 Romain Manni-Bucau
 Twitter: @rmannibucau
 Blog: http://rmannibucau.wordpress.com/
 LinkedIn: http://fr.linkedin.com/in/rmannibucau
 Github: https://github.com/rmannibucau



 2013/11/6 Alex The Rocker alex.m3...@gmail.com:
  Romain:
 
  Yes, the TestAppBase class is the base abstract class of the TestApp
 class
  which is JAX-RS annotated.
 
  Actually, the .jar file I attached is correct, but it has to be put in
 the
  WEB-INF/lib of a web app which causes this .jar file to be loaded when
 the
  webapp starts.
 
  So you can definitly use this .jar to reproduce our issue and check if
 your
  fix idea works.
 
  I can very quickly test on our real app if you have a few test .jar
 files
  which I can use to replace TomEE+221's
 
  thanks,
  Alex
 
 
 
  On Wed, Nov 6, 2013 at 1:27 PM, Romain Manni-Bucau 
 rmannibu...@gmail.comwrote:
 
  Is you Base class abstract? If so I have an idea of the issue. If
 not Ill
  look in the afternoon
  Le 6 nov. 2013 13:10, Alex The Rocker alex.m3...@gmail.com a
 écrit :
 
   hold on, I sent the wrong version of the sample...
  
  
   On Wed, Nov 6, 2013 at 12:57 PM, Alex The Rocker 
 alex.m3...@gmail.com
   wrote:
  
Romain:
   
Thanks for fast answer.
Unfortunately I never rebuilt TomEE,could you post a prebuilt
 .jar(s) ?
In the meantime, I had a developer who provided a minimal sample
 which
allow reproducing the issue with TomEE+ 1.6.0 snapshot 221.
   
Please find it attached (with .java sources in the .jar)
   
Do you mean the issue is supposed to be fixed in today's nightly
  build's
snapshot?
   
best regards,
Alexandre
   
   
On Wed, Nov 6, 2013 at 11:42 AM, Romain Manni-Bucau 
   rmannibu...@gmail.com
 wrote:
   
Hi
   
if you can rebuild tomee from sources would be great if you can re
  test
now
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
   
   
   
2013/11/6 Alex The Rocker alex.m3...@gmail.com:
 Hello,

 I have a critical issue with our Web application using
 TomEE1.6.0+Snapshot221 : the web app can't start an fails with
 an
 instantion error on a parent abstract class of a class
 implementing
  a
 JAX-RS service.

 This is a regression over the TomEE+ 1.6.0 snapshot 140 which
 we've
   been
 using so far.

 See below the error message in catalina.out.
 What kind of traces/logging can I activate (please provide clear
 instructions which can be applied by people not aware of TomEE
   internal,
 like change XXX in file XX then restart) in order to get a
 better
 understanding on whether the issue comes from our app or from
 TomEE?

 Thanks,
 Alex
 

 SEVERE: Unable to deploy collapsed ear in war
 StandardEngine[Catalina].StandardH
 ost[localhost].StandardContext[/acme]
 org.apache.openejb.OpenEJBException: Unable to instantiate
  Application
 class: com.acme.platform.restServices.ModelerBase:
 com.acme.platform.restServices.ModelerBase
 at

   
  
 
 org.apache.openejb.config.AnnotationDeployer$ProcessAnnotatedBeans.deploy(AnnotationDeployer.java:2025)
 at

   
  
 
 org.apache.openejb.config.AnnotationDeployer$ProcessAnnotatedBeans.deploy(AnnotationDeployer.java:1820)
 at

   
  
 
 org.apache.openejb.config.AnnotationDeployer.deploy(AnnotationDeployer.java:355)
 at

   
  
 
 org.apache.openejb.config.ConfigurationFactory$Chain.deploy(ConfigurationFactory.java:396)
 at

   
  
 
 org.apache.openejb.config.ConfigurationFactory.configureApplication(ConfigurationFactory.java:938)
 at

   
  
 
 org.apache.tomee.catalina.TomcatWebAppBuilder.startInternal(TomcatWebAppBuilder.java:1171)
 at

   
  
 
 org.apache.tomee.catalina.TomcatWebAppBuilder.configureStart(TomcatWebAppBuilder.java:1051

Blocking issue with TomEE1.6.0+Snapshot221: can't start because REST parent abstract class instanciation error

[Alex The Rocker]

Hello,

I have a critical issue with our Web application using
TomEE1.6.0+Snapshot221 : the web app can't start an fails with an
instantion error on a parent abstract class of a class implementing a
JAX-RS service.

This is a regression over the TomEE+ 1.6.0 snapshot 140 which we've been
using so far.

See below the error message in catalina.out.
What kind of traces/logging can I activate (please provide clear
instructions which can be applied by people not aware of TomEE internal,
like change XXX in file XX then restart) in order to get a better
understanding on whether the issue comes from our app or from TomEE?

Thanks,
Alex


SEVERE: Unable to deploy collapsed ear in war
StandardEngine[Catalina].StandardH
ost[localhost].StandardContext[/acme]
org.apache.openejb.OpenEJBException: Unable to instantiate Application
class: com.acme.platform.restServices.ModelerBase:
com.acme.platform.restServices.ModelerBase
at
org.apache.openejb.config.AnnotationDeployer$ProcessAnnotatedBeans.deploy(AnnotationDeployer.java:2025)
at
org.apache.openejb.config.AnnotationDeployer$ProcessAnnotatedBeans.deploy(AnnotationDeployer.java:1820)
at
org.apache.openejb.config.AnnotationDeployer.deploy(AnnotationDeployer.java:355)
at
org.apache.openejb.config.ConfigurationFactory$Chain.deploy(ConfigurationFactory.java:396)
at
org.apache.openejb.config.ConfigurationFactory.configureApplication(ConfigurationFactory.java:938)
at
org.apache.tomee.catalina.TomcatWebAppBuilder.startInternal(TomcatWebAppBuilder.java:1171)
at
org.apache.tomee.catalina.TomcatWebAppBuilder.configureStart(TomcatWebAppBuilder.java:1051)
at
org.apache.tomee.catalina.GlobalListenerSupport.lifecycleEvent(GlobalListenerSupport.java:127)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at
org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5322)
at
org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
at
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
at
org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1120)
at
org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1678)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:780)

Re: Blocking issue with TomEE1.6.0+Snapshot221: can't start because REST parent abstract class instanciation error

[Alex The Rocker]

Romain:

Thanks for fast answer.
Unfortunately I never rebuilt TomEE,could you post a prebuilt .jar(s) ?
In the meantime, I had a developer who provided a minimal sample which
allow reproducing the issue with TomEE+ 1.6.0 snapshot 221.

Please find it attached (with .java sources in the .jar)

Do you mean the issue is supposed to be fixed in today's nightly build's
snapshot?

best regards,
Alexandre


On Wed, Nov 6, 2013 at 11:42 AM, Romain Manni-Bucau
rmannibu...@gmail.comwrote:

 Hi

 if you can rebuild tomee from sources would be great if you can re test now
 Romain Manni-Bucau
 Twitter: @rmannibucau
 Blog: http://rmannibucau.wordpress.com/
 LinkedIn: http://fr.linkedin.com/in/rmannibucau
 Github: https://github.com/rmannibucau



 2013/11/6 Alex The Rocker alex.m3...@gmail.com:
  Hello,
 
  I have a critical issue with our Web application using
  TomEE1.6.0+Snapshot221 : the web app can't start an fails with an
  instantion error on a parent abstract class of a class implementing a
  JAX-RS service.
 
  This is a regression over the TomEE+ 1.6.0 snapshot 140 which we've been
  using so far.
 
  See below the error message in catalina.out.
  What kind of traces/logging can I activate (please provide clear
  instructions which can be applied by people not aware of TomEE internal,
  like change XXX in file XX then restart) in order to get a better
  understanding on whether the issue comes from our app or from TomEE?
 
  Thanks,
  Alex
  
 
  SEVERE: Unable to deploy collapsed ear in war
  StandardEngine[Catalina].StandardH
  ost[localhost].StandardContext[/acme]
  org.apache.openejb.OpenEJBException: Unable to instantiate Application
  class: com.acme.platform.restServices.ModelerBase:
  com.acme.platform.restServices.ModelerBase
  at
 
 org.apache.openejb.config.AnnotationDeployer$ProcessAnnotatedBeans.deploy(AnnotationDeployer.java:2025)
  at
 
 org.apache.openejb.config.AnnotationDeployer$ProcessAnnotatedBeans.deploy(AnnotationDeployer.java:1820)
  at
 
 org.apache.openejb.config.AnnotationDeployer.deploy(AnnotationDeployer.java:355)
  at
 
 org.apache.openejb.config.ConfigurationFactory$Chain.deploy(ConfigurationFactory.java:396)
  at
 
 org.apache.openejb.config.ConfigurationFactory.configureApplication(ConfigurationFactory.java:938)
  at
 
 org.apache.tomee.catalina.TomcatWebAppBuilder.startInternal(TomcatWebAppBuilder.java:1171)
  at
 
 org.apache.tomee.catalina.TomcatWebAppBuilder.configureStart(TomcatWebAppBuilder.java:1051)
  at
 
 org.apache.tomee.catalina.GlobalListenerSupport.lifecycleEvent(GlobalListenerSupport.java:127)
  at
 
 org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
  at
 
 org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
  at
 
 org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5322)
  at
  org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
  at
 
 org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
  at
  org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
  at
  org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
  at
 
 org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1120)
  at
 
 org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1678)
  at
  java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
  at
  java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
  at java.util.concurrent.FutureTask.run(FutureTask.java:166)
  at
 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
  at
 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
  at java.lang.Thread.run(Thread.java:780)



tomee-sample.jar
Description: application/java-archive

Re: Blocking issue with TomEE1.6.0+Snapshot221: can't start because REST parent abstract class instanciation error

[Alex The Rocker]

hold on, I sent the wrong version of the sample...


On Wed, Nov 6, 2013 at 12:57 PM, Alex The Rocker alex.m3...@gmail.comwrote:

 Romain:

 Thanks for fast answer.
 Unfortunately I never rebuilt TomEE,could you post a prebuilt .jar(s) ?
 In the meantime, I had a developer who provided a minimal sample which
 allow reproducing the issue with TomEE+ 1.6.0 snapshot 221.

 Please find it attached (with .java sources in the .jar)

 Do you mean the issue is supposed to be fixed in today's nightly build's
 snapshot?

 best regards,
 Alexandre


 On Wed, Nov 6, 2013 at 11:42 AM, Romain Manni-Bucau rmannibu...@gmail.com
  wrote:

 Hi

 if you can rebuild tomee from sources would be great if you can re test
 now
 Romain Manni-Bucau
 Twitter: @rmannibucau
 Blog: http://rmannibucau.wordpress.com/
 LinkedIn: http://fr.linkedin.com/in/rmannibucau
 Github: https://github.com/rmannibucau



 2013/11/6 Alex The Rocker alex.m3...@gmail.com:
  Hello,
 
  I have a critical issue with our Web application using
  TomEE1.6.0+Snapshot221 : the web app can't start an fails with an
  instantion error on a parent abstract class of a class implementing a
  JAX-RS service.
 
  This is a regression over the TomEE+ 1.6.0 snapshot 140 which we've been
  using so far.
 
  See below the error message in catalina.out.
  What kind of traces/logging can I activate (please provide clear
  instructions which can be applied by people not aware of TomEE internal,
  like change XXX in file XX then restart) in order to get a better
  understanding on whether the issue comes from our app or from TomEE?
 
  Thanks,
  Alex
  
 
  SEVERE: Unable to deploy collapsed ear in war
  StandardEngine[Catalina].StandardH
  ost[localhost].StandardContext[/acme]
  org.apache.openejb.OpenEJBException: Unable to instantiate Application
  class: com.acme.platform.restServices.ModelerBase:
  com.acme.platform.restServices.ModelerBase
  at
 
 org.apache.openejb.config.AnnotationDeployer$ProcessAnnotatedBeans.deploy(AnnotationDeployer.java:2025)
  at
 
 org.apache.openejb.config.AnnotationDeployer$ProcessAnnotatedBeans.deploy(AnnotationDeployer.java:1820)
  at
 
 org.apache.openejb.config.AnnotationDeployer.deploy(AnnotationDeployer.java:355)
  at
 
 org.apache.openejb.config.ConfigurationFactory$Chain.deploy(ConfigurationFactory.java:396)
  at
 
 org.apache.openejb.config.ConfigurationFactory.configureApplication(ConfigurationFactory.java:938)
  at
 
 org.apache.tomee.catalina.TomcatWebAppBuilder.startInternal(TomcatWebAppBuilder.java:1171)
  at
 
 org.apache.tomee.catalina.TomcatWebAppBuilder.configureStart(TomcatWebAppBuilder.java:1051)
  at
 
 org.apache.tomee.catalina.GlobalListenerSupport.lifecycleEvent(GlobalListenerSupport.java:127)
  at
 
 org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
  at
 
 org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
  at
 
 org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5322)
  at
  org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
  at
 
 org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
  at
  org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
  at
  org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
  at
 
 org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1120)
  at
 
 org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1678)
  at
  java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
  at
  java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
  at java.util.concurrent.FutureTask.run(FutureTask.java:166)
  at
 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
  at
 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
  at java.lang.Thread.run(Thread.java:780)

Re: Blocking issue with TomEE1.6.0+Snapshot221: can't start because REST parent abstract class instanciation error

[Alex The Rocker]

Romain:

First tests are positive (and the sample is now OK) ; but to be 100% sure I
have delivered this fix version into our automated test system for a full
nightly replay of our test cases. Tomorrow I'll have the final word on this.

Thanks (a lot),

Alex.



On Wed, Nov 6, 2013 at 3:07 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote:

 here is a tomee
 http://people.apache.org/~rmannibucau/apache-tomee-plus-1.6.0-SNAPSHOT.zip
 Romain Manni-Bucau
 Twitter: @rmannibucau
 Blog: http://rmannibucau.wordpress.com/
 LinkedIn: http://fr.linkedin.com/in/rmannibucau
 Github: https://github.com/rmannibucau



 2013/11/6 Alex The Rocker alex.m3...@gmail.com:
  Romain:
 
  Yes, the TestAppBase class is the base abstract class of the TestApp
 class
  which is JAX-RS annotated.
 
  Actually, the .jar file I attached is correct, but it has to be put in
 the
  WEB-INF/lib of a web app which causes this .jar file to be loaded when
 the
  webapp starts.
 
  So you can definitly use this .jar to reproduce our issue and check if
 your
  fix idea works.
 
  I can very quickly test on our real app if you have a few test .jar files
  which I can use to replace TomEE+221's
 
  thanks,
  Alex
 
 
 
  On Wed, Nov 6, 2013 at 1:27 PM, Romain Manni-Bucau 
 rmannibu...@gmail.comwrote:
 
  Is you Base class abstract? If so I have an idea of the issue. If not
 Ill
  look in the afternoon
  Le 6 nov. 2013 13:10, Alex The Rocker alex.m3...@gmail.com a écrit
 :
 
   hold on, I sent the wrong version of the sample...
  
  
   On Wed, Nov 6, 2013 at 12:57 PM, Alex The Rocker 
 alex.m3...@gmail.com
   wrote:
  
Romain:
   
Thanks for fast answer.
Unfortunately I never rebuilt TomEE,could you post a prebuilt
 .jar(s) ?
In the meantime, I had a developer who provided a minimal sample
 which
allow reproducing the issue with TomEE+ 1.6.0 snapshot 221.
   
Please find it attached (with .java sources in the .jar)
   
Do you mean the issue is supposed to be fixed in today's nightly
  build's
snapshot?
   
best regards,
Alexandre
   
   
On Wed, Nov 6, 2013 at 11:42 AM, Romain Manni-Bucau 
   rmannibu...@gmail.com
 wrote:
   
Hi
   
if you can rebuild tomee from sources would be great if you can re
  test
now
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
   
   
   
2013/11/6 Alex The Rocker alex.m3...@gmail.com:
 Hello,

 I have a critical issue with our Web application using
 TomEE1.6.0+Snapshot221 : the web app can't start an fails with an
 instantion error on a parent abstract class of a class
 implementing
  a
 JAX-RS service.

 This is a regression over the TomEE+ 1.6.0 snapshot 140 which
 we've
   been
 using so far.

 See below the error message in catalina.out.
 What kind of traces/logging can I activate (please provide clear
 instructions which can be applied by people not aware of TomEE
   internal,
 like change XXX in file XX then restart) in order to get a
 better
 understanding on whether the issue comes from our app or from
 TomEE?

 Thanks,
 Alex
 

 SEVERE: Unable to deploy collapsed ear in war
 StandardEngine[Catalina].StandardH
 ost[localhost].StandardContext[/acme]
 org.apache.openejb.OpenEJBException: Unable to instantiate
  Application
 class: com.acme.platform.restServices.ModelerBase:
 com.acme.platform.restServices.ModelerBase
 at

   
  
 
 org.apache.openejb.config.AnnotationDeployer$ProcessAnnotatedBeans.deploy(AnnotationDeployer.java:2025)
 at

   
  
 
 org.apache.openejb.config.AnnotationDeployer$ProcessAnnotatedBeans.deploy(AnnotationDeployer.java:1820)
 at

   
  
 
 org.apache.openejb.config.AnnotationDeployer.deploy(AnnotationDeployer.java:355)
 at

   
  
 
 org.apache.openejb.config.ConfigurationFactory$Chain.deploy(ConfigurationFactory.java:396)
 at

   
  
 
 org.apache.openejb.config.ConfigurationFactory.configureApplication(ConfigurationFactory.java:938)
 at

   
  
 
 org.apache.tomee.catalina.TomcatWebAppBuilder.startInternal(TomcatWebAppBuilder.java:1171)
 at

   
  
 
 org.apache.tomee.catalina.TomcatWebAppBuilder.configureStart(TomcatWebAppBuilder.java:1051)
 at

   
  
 
 org.apache.tomee.catalina.GlobalListenerSupport.lifecycleEvent(GlobalListenerSupport.java:127)
 at

   
  
 
 org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
 at

   
  
 
 org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
 at

   
  
 
 org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5322

TomEE support lifecycle

[Alex The Rocker]

Hello,

Unless i'm mistaking, there's no information on tomee.apache.org about
TomEE support lifecycle, or EOL (End Of Life) policy.

I see in JIRA that there's an on going 1.5.3 branch, and 1.6.0 is not yet
released as final.


My company products' previous release was certified with TomEE 1.5.2, and
we target 1.6.0 for the new release. We expect TomEE 1.5.x to be still
available for a while because our customer's won't jump at once to our new
release.

I think we need a clear lifecycle / EOL policy. As an example, Tomcat's
policy to support 3 major releases (they EOLed Tomcat 5.x when they
released Tomcat 8) sounds good.

Could TomEE come with an EOL policy similar to Tomcat's ?

thanks,
Alex

Re: 1.6.0 release plans?

[Alex The Rocker]

Hi,

Is TomEE 1.6 release candidate something feasible this upcoming week (week
45) ?
I can have large non-reg testing with our apps as soon as this release
candidate is available...

Thanks,
Alex.



On Wed, Oct 30, 2013 at 12:37 PM, Howard W. Smith, Jr. 
smithh032...@gmail.com wrote:

 understood, thanks. :)




 On Wed, Oct 30, 2013 at 7:34 AM, Romain Manni-Bucau
 rmannibu...@gmail.comwrote:

  this has been discussed on a lot of threads, we target 1.6 ATM then
  see to do a +1 version (2, 5 maybe 7, still under discussion) but
  this one will be obviously based on tomcat 8 + the whole apache EE 7
  stack
  Romain Manni-Bucau
  Twitter: @rmannibucau
  Blog: http://rmannibucau.wordpress.com/
  LinkedIn: http://fr.linkedin.com/in/rmannibucau
  Github: https://github.com/rmannibucau
 
 
 
  2013/10/30 Howard W. Smith, Jr. smithh032...@gmail.com:
   interesting response. well, tomcat 8 + myfaces 2.2 + some other
  components
   = tomee (javaee 7), right? tomcat 8 and myfaces 2.2 have already
  released.
  
   does tomee 1.7 (snapshot) = (possible) javaee 7 version/release?
  
  
  
   On Wed, Oct 30, 2013 at 1:46 AM, Romain Manni-Bucau
   rmannibu...@gmail.comwrote:
  
   When tomee will target javaee 7
   Le 30 oct. 2013 05:26, Howard W. Smith, Jr. smithh032...@gmail.com
 
  a
   écrit :
  
Mark, since you mentioned somewhat of a road map, maybe you, Romain,
  or
   one
of the others can tell us when will MyFaces 2.2 be bundled with
  tomee(+)
   ?
   
I would love to start using MyFaces 2.2 with tomee, but i don't want
  to
   use
that until it is bundled in ZIP file. just a personal preference of
  mine.
   
   
On Tue, Oct 29, 2013 at 4:16 PM, Mark Struberg strub...@yahoo.de
   wrote:
   
 yup, gonna start with cutting the actual release in a few hours.

 The next projects on the list are xbean and OpenWebBeans.

 LieGrue,
 strub




 - Original Message -
  From: Romain Manni-Bucau rmannibu...@gmail.com
  To: users@tomee.apache.org users@tomee.apache.org
  Cc:
  Sent: Tuesday, 29 October 2013, 17:14
  Subject: Re: 1.6.0 release plans?
 
  Hi
 
  OpenJPA release work started, Jira are almost closed and the
  release
  should start soon
  Romain Manni-Bucau
  Twitter: @rmannibucau
  Blog: http://rmannibucau.wordpress.com/
  LinkedIn: http://fr.linkedin.com/in/rmannibucau
  Github: https://github.com/rmannibucau
 
 
 
 
  2013/10/29 Alex The Rocker alex.m3...@gmail.com:
   Hello TomEE team,
 
   Would you please update us with TomEE 1.6.0 official release?
   For example, was the action mentionned by jean-Louis on
 OpenJPA
   done?
   When is planned something like an official beta or release
  candidate ?
 
   Thanks,
   Alex.
 
 
 
   On Wed, Oct 9, 2013 at 9:04 AM, Jean-Louis MONTEIRO
  jeano...@gmail.comwrote:
 
   First, push an official mail on OpenJPA mailling list asking
  for a
  2.3.0
   release. Waiting an answer within the usual 72 hours for
  example.
   If no answer or no way to get a release by October 20th or so
  (I
  don't
   care), then fork it internally as we did sometimes in the
 past
  and
  start
   releasing TomEE by end of November.
 
   That means more or less that we must freeze/finalize all
  on-going
   development by October the 15th I think.
 
   Thoughts?
 
   Jean-Louis
 
 
   2013/10/8 Romain Manni-Bucau rmannibu...@gmail.com
 
Technically yes, then the issue is we need somebody with
 all
   perms
  to
release tomee (ping @David?).
   
*Romain Manni-Bucau*
*Twitter: @rmannibucau https://twitter.com/rmannibucau*
*Blog: **http://rmannibucau.wordpress.com/*
http://rmannibucau.wordpress.com/
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
   
   
   
2013/10/8 Alex The Rocker alex.m3...@gmail.com
   
 @Romain, not sure to understand the details, but do you
  mean
  you may
have a
 way to release TomEE+ 1.6.0 official release without
  waiting
  for the
 (unknown) OpenJPA 2.3.0 release?

 Thanks,
 Alex


 On Tue, Oct 8, 2013 at 4:55 PM, Romain Manni-Bucau 
rmannibu...@gmail.com
 wrote:

  I meant forking it for the release as usual,
  not using a snapshot
which
  wouldn't be professional
 
  *Romain Manni-Bucau*
  *Twitter: @rmannibucau
  https://twitter.com/rmannibucau*
  *Blog: **http://rmannibucau.wordpress.com/*
  http://rmannibucau.wordpress.com/
  *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
  *Github: https://github.com/rmannibucau

Re: 1.6.0 release plans?

[Alex The Rocker]

+1, we also need in my company an official TomEE 1.6.0 Generally
Available release (i.e., not Snapshot release), no later than mid-november
; so I guess beta/rc should start ASAP this month.

@TomEE team, is this schedule possible?

thanks,
Alex




On Mon, Oct 7, 2013 at 9:50 PM, Jim Ancona j...@anconafamily.com wrote:

 Is there any plan for a TomEE 1.6 release? I'm working on plans for a
 fairly large deployment and there are several issues that we'd like to have
 available, so any info you can provide would be appreciated.

 Thanks!

 Jim

Re: 1.6.0 release plans?

[Alex The Rocker]

@Romain: which OpenJPA release are you waiting to make TomEE 1.6.0
generally available, and what is this OpenJPA release's schedule?

Thanks,
Alex


On Tue, Oct 8, 2013 at 11:01 AM, zmirc m_chi...@yahoo.com wrote:

 I would really want to know that, too.



 --
 View this message in context:
 http://openejb.979440.n4.nabble.com/1-6-0-release-plans-tp4665437p4665447.html
 Sent from the OpenEJB User mailing list archive at Nabble.com.

Re: 1.6.0 release plans?

[Alex The Rocker]

From OpenJPA's web site:
=
The 2.x releases http://openjpa.apache.org/downloads.html (2.2.2 is the
latest) are a production ready, compliant implementation of the JSR-317
Java Persistence 2.0 http://jcp.org/en/jsr/detail?id=317 specification,
which is backwards compatible to the JPA 1.0 specification and passes the
Sun JPA 2.0 Technology Compatibility Kit.

The upcoming 2.3 release is based off of the 2.2.x release stream and will
contain some additional features (TBD).
=

No way to know when OpenJPA 2.3 could be available.

Can't we have a TomEE 1.6.0 release based on OpenJPA 2.2.2 which is already
TCK compliant, and leave OpenJPA 2.3 for a future TomEE release?


Thanks,

Alex


On Tue, Oct 8, 2013 at 2:21 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote:

 @Alex: 2.3.0, there are working on it but want to address few blocking
 issues before AFAIK

 *Romain Manni-Bucau*
 *Twitter: @rmannibucau https://twitter.com/rmannibucau*
 *Blog: **http://rmannibucau.wordpress.com/*
 http://rmannibucau.wordpress.com/
 *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
 *Github: https://github.com/rmannibucau*



 2013/10/8 Alex The Rocker alex.m3...@gmail.com

  @Romain: which OpenJPA release are you waiting to make TomEE 1.6.0
  generally available, and what is this OpenJPA release's schedule?
 
  Thanks,
  Alex
 
 
  On Tue, Oct 8, 2013 at 11:01 AM, zmirc m_chi...@yahoo.com wrote:
 
   I would really want to know that, too.
  
  
  
   --
   View this message in context:
  
 
 http://openejb.979440.n4.nabble.com/1-6-0-release-plans-tp4665437p4665447.html
   Sent from the OpenEJB User mailing list archive at Nabble.com.
  
 

Re: 1.6.0 release plans?

[Alex The Rocker]

Otherwise, can a TomEE 1.6.0 official release be make with a snapshot
OpenJPA 2.3 ?

I'm concerned if we have no visibility

Thanks,
Alex




On Tue, Oct 8, 2013 at 2:46 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote:

 Would mean reverting some code in openejb + forking openwebbeans and update
 the code + accepting to not work in some cases in java 7...so I don't think
 so.


 *Romain Manni-Bucau*
 *Twitter: @rmannibucau https://twitter.com/rmannibucau*
 *Blog: **http://rmannibucau.wordpress.com/*
 http://rmannibucau.wordpress.com/
 *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
 *Github: https://github.com/rmannibucau*



 2013/10/8 Alex The Rocker alex.m3...@gmail.com

  From OpenJPA's web site:
 
 
 =
  The 2.x releases http://openjpa.apache.org/downloads.html (2.2.2 is
 the
  latest) are a production ready, compliant implementation of the JSR-317
  Java Persistence 2.0 http://jcp.org/en/jsr/detail?id=317
 specification,
  which is backwards compatible to the JPA 1.0 specification and passes the
  Sun JPA 2.0 Technology Compatibility Kit.
 
  The upcoming 2.3 release is based off of the 2.2.x release stream and
 will
  contain some additional features (TBD).
 
 
 =
 
  No way to know when OpenJPA 2.3 could be available.
 
  Can't we have a TomEE 1.6.0 release based on OpenJPA 2.2.2 which is
 already
  TCK compliant, and leave OpenJPA 2.3 for a future TomEE release?
 
 
  Thanks,
 
  Alex
 
 
  On Tue, Oct 8, 2013 at 2:21 PM, Romain Manni-Bucau 
 rmannibu...@gmail.com
  wrote:
 
   @Alex: 2.3.0, there are working on it but want to address few blocking
   issues before AFAIK
  
   *Romain Manni-Bucau*
   *Twitter: @rmannibucau https://twitter.com/rmannibucau*
   *Blog: **http://rmannibucau.wordpress.com/*
   http://rmannibucau.wordpress.com/
   *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
   *Github: https://github.com/rmannibucau*
  
  
  
   2013/10/8 Alex The Rocker alex.m3...@gmail.com
  
@Romain: which OpenJPA release are you waiting to make TomEE 1.6.0
generally available, and what is this OpenJPA release's schedule?
   
Thanks,
Alex
   
   
On Tue, Oct 8, 2013 at 11:01 AM, zmirc m_chi...@yahoo.com wrote:
   
 I would really want to know that, too.



 --
 View this message in context:

   
  
 
 http://openejb.979440.n4.nabble.com/1-6-0-release-plans-tp4665437p4665447.html
 Sent from the OpenEJB User mailing list archive at Nabble.com.

   
  
 

Re: 1.6.0 release plans?

[Alex The Rocker]

@Romain, not sure to understand the details, but do you mean you may have a
way to release TomEE+ 1.6.0 official release without waiting for the
(unknown) OpenJPA 2.3.0 release?

Thanks,
Alex


On Tue, Oct 8, 2013 at 4:55 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote:

 I meant forking it for the release as usual, not using a snapshot which
 wouldn't be professional

 *Romain Manni-Bucau*
 *Twitter: @rmannibucau https://twitter.com/rmannibucau*
 *Blog: **http://rmannibucau.wordpress.com/*
 http://rmannibucau.wordpress.com/
 *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
 *Github: https://github.com/rmannibucau*



 2013/10/8 Jean-Louis MONTEIRO jeano...@gmail.com

  Possible, but I would only release TomEE itself not all modules to avoid
  depending on a snapshot.
  TomEE is different because if the snapshot is available during the build,
  which is obviously the case, we can embedded the JAR file in the zip
 file.
 
  JLouis
 
 
  2013/10/8 Romain Manni-Bucau rmannibu...@gmail.com
 
   technically it is possible
  
   *Romain Manni-Bucau*
   *Twitter: @rmannibucau https://twitter.com/rmannibucau*
   *Blog: **http://rmannibucau.wordpress.com/*
   http://rmannibucau.wordpress.com/
   *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
   *Github: https://github.com/rmannibucau*
  
  
  
   2013/10/8 Alex The Rocker alex.m3...@gmail.com
  
Otherwise, can a TomEE 1.6.0 official release be make with a snapshot
OpenJPA 2.3 ?
   
I'm concerned if we have no visibility
   
Thanks,
Alex
   
   
   
   
On Tue, Oct 8, 2013 at 2:46 PM, Romain Manni-Bucau 
   rmannibu...@gmail.com
wrote:
   
 Would mean reverting some code in openejb + forking openwebbeans
 and
update
 the code + accepting to not work in some cases in java 7...so I
 don't
think
 so.


 *Romain Manni-Bucau*
 *Twitter: @rmannibucau https://twitter.com/rmannibucau*
 *Blog: **http://rmannibucau.wordpress.com/*
 http://rmannibucau.wordpress.com/
 *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
 *Github: https://github.com/rmannibucau*



 2013/10/8 Alex The Rocker alex.m3...@gmail.com

  From OpenJPA's web site:
 
 

   
  
 
 =
  The 2.x releases http://openjpa.apache.org/downloads.html
 (2.2.2
   is
 the
  latest) are a production ready, compliant implementation of the
   JSR-317
  Java Persistence 2.0 http://jcp.org/en/jsr/detail?id=317
 specification,
  which is backwards compatible to the JPA 1.0 specification and
  passes
the
  Sun JPA 2.0 Technology Compatibility Kit.
 
  The upcoming 2.3 release is based off of the 2.2.x release stream
  and
 will
  contain some additional features (TBD).
 
 

   
  
 
 =
 
  No way to know when OpenJPA 2.3 could be available.
 
  Can't we have a TomEE 1.6.0 release based on OpenJPA 2.2.2 which
 is
 already
  TCK compliant, and leave OpenJPA 2.3 for a future TomEE release?
 
 
  Thanks,
 
  Alex
 
 
  On Tue, Oct 8, 2013 at 2:21 PM, Romain Manni-Bucau 
 rmannibu...@gmail.com
  wrote:
 
   @Alex: 2.3.0, there are working on it but want to address few
blocking
   issues before AFAIK
  
   *Romain Manni-Bucau*
   *Twitter: @rmannibucau https://twitter.com/rmannibucau*
   *Blog: **http://rmannibucau.wordpress.com/*
   http://rmannibucau.wordpress.com/
   *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
   *Github: https://github.com/rmannibucau*
  
  
  
   2013/10/8 Alex The Rocker alex.m3...@gmail.com
  
@Romain: which OpenJPA release are you waiting to make TomEE
   1.6.0
generally available, and what is this OpenJPA release's
  schedule?
   
Thanks,
Alex
   
   
On Tue, Oct 8, 2013 at 11:01 AM, zmirc m_chi...@yahoo.com
   wrote:
   
 I would really want to know that, too.



 --
 View this message in context:

   
  
 

   
  
 
 http://openejb.979440.n4.nabble.com/1-6-0-release-plans-tp4665437p4665447.html
 Sent from the OpenEJB User mailing list archive at
  Nabble.com.

   
  
 

   
  
 
 
 
  --
  Jean-Louis
 

Re: How far are we from a TomEE 1.5.2 release?

[Alex The Rocker]

Hello,

We need the fix fo TOMEE-669https://issues.apache.org/jira/browse/TOMEE-669,
but I according to the person who fixed it, the fix was committed with
TOMEE-668 https://issues.apache.org/jira/browse/TOMEE-668.
Would you agree to make it part of 1.5.2 fix release?

Thanks,
Alexandre


On Wed, Feb 27, 2013 at 7:49 PM, David Blevins david.blev...@gmail.comwrote:

 Alex and everyone who prefers 1.5.2 over 1.6.0,

 If we were to branch from the 1.5.1 and add merge fixes to make that the
 next 1.5.2, do you know which fixes you would need?  Or if there was a
 point of time where you thought 1.5.2 was good, that helps too.

 Getting an idea of what exactly people need will help significantly.  If
 we pick an arbitrary date between 1.5.1 and now and call that 1.5.2 final,
 we may or may not be close to what people actually need.


 -David

 On Feb 26, 2013, at 5:59 AM, Alex The Rocker alex.m3...@gmail.com wrote:

  what's you best guess for a 1.5.2 release ?
 
 
 
 
  On Tue, Feb 26, 2013 at 2:17 PM, Howard W. Smith, Jr. 
  smithh032...@gmail.com wrote:
 
  What JIRA for that issue? 1.6.0 snapshot as well as latest 1.5.2
 SNAPSHOT
  working great for me in production.
  On Feb 26, 2013 8:12 AM, Romain Manni-Bucau rmannibu...@gmail.com
  wrote:
 
  Hi,
 
  after our last discussions we upgraded the 1.5.2-SNAPSHOT version to
  1.6.0-SNAPSHOT (our trunk).
 
  No work started on 1.5.2. I wanted to help preparing the release 1.6.0
  but
  we have ATM some infra issue due to the renaming of the project (will
  be
  fixed soon).
 
  *Romain Manni-Bucau*
  *Twitter: @rmannibucau https://twitter.com/rmannibucau*
  *Blog: **http://rmannibucau.wordpress.com/*
  http://rmannibucau.wordpress.com/
  *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
  *Github: https://github.com/rmannibucau*
 
 
 
  2013/2/26 Alex The Rocker alex.m3...@gmail.com
 
  Hello,
 
 
  Some portions of our app depends on a fix made available in TomEE
 1.5.2
  Snapshots early in January. Since TomEE 1.5.2 is not officially
  released,
  we cannot rely on it yet.
 
  Would it be possible to have a TomEE 1.5.2 release schedule?
 
  Also,
 
 
 
 
 https://repository.apache.org/content/groups/snapshots/org/apache/openejb/apache-tomee/1.5.2-SNAPSHOT/directory
  has no new 1.5.2 Snapshot since 13th of February, should be use
  this one in order to perform our non-regression tests?
 
  Thansk,
  Alex
 
 
 

Re: How far are we from a TomEE 1.5.2 release?

[Alex The Rocker]

what's you best guess for a 1.5.2 release ?




On Tue, Feb 26, 2013 at 2:17 PM, Howard W. Smith, Jr. 
smithh032...@gmail.com wrote:

 What JIRA for that issue? 1.6.0 snapshot as well as latest 1.5.2 SNAPSHOT
 working great for me in production.
  On Feb 26, 2013 8:12 AM, Romain Manni-Bucau rmannibu...@gmail.com
 wrote:

  Hi,
 
  after our last discussions we upgraded the 1.5.2-SNAPSHOT version to
  1.6.0-SNAPSHOT (our trunk).
 
  No work started on 1.5.2. I wanted to help preparing the release 1.6.0
 but
  we have ATM some infra issue due to the renaming of the project (will
 be
  fixed soon).
 
  *Romain Manni-Bucau*
  *Twitter: @rmannibucau https://twitter.com/rmannibucau*
  *Blog: **http://rmannibucau.wordpress.com/*
  http://rmannibucau.wordpress.com/
  *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
  *Github: https://github.com/rmannibucau*
 
 
 
  2013/2/26 Alex The Rocker alex.m3...@gmail.com
 
   Hello,
  
  
   Some portions of our app depends on a fix made available in TomEE 1.5.2
   Snapshots early in January. Since TomEE 1.5.2 is not officially
 released,
   we cannot rely on it yet.
  
   Would it be possible to have a TomEE 1.5.2 release schedule?
  
   Also,
  
  
 
 https://repository.apache.org/content/groups/snapshots/org/apache/openejb/apache-tomee/1.5.2-SNAPSHOT/directory
   has no new 1.5.2 Snapshot since 13th of February, should be use
   this one in order to perform our non-regression tests?
  
   Thansk,
   Alex
  
 

Re: TomEE 1.5.2 regression over 1.5.1: error invoking org.apache.openejb.observer.ObserverManager$Observer

[Alex The Rocker]

Romain:

I don't know what's subresource locator, many developers contribute to this
application (~200 .jar files in the web app!).
I have taken the time to reduce the web app to a minimum size that still
leads to same error at deployment time, and I have opened
https://issues.apache.org/jira/browse/TOMEE-773 JIRA.

I don't understand your remark about 1.5.2 (you mention it still doesn't
exist), can it be fixed on 1.5.2 or only on 1.6.0 ?

Thanks,
Alex



On Sun, Feb 17, 2013 at 11:46 AM, Romain Manni-Bucau
rmannibu...@gmail.comwrote:

 Ps: do you use subresource locator?
 Le 17 févr. 2013 10:33, Romain Manni-Bucau rmannibu...@gmail.com a
 écrit :

  Hi
 
  First trunk is 1.6.0 snapshot (1.5.2 still doesnt exist)
 
  Then this is a small bug IMO. If you can reproduce it, it will help but
 it
  will be fixed soon normally
  Le 16 févr. 2013 23:54, Alex The Rocker alex.m3...@gmail.com a
 écrit :
 
  Hello:
 
  Our application which works fine with TomEE+ 1.5.1 miserably fails at
  startup with the following trace in catalina.out. The issue is so
 severe
  that it's not deployed at all.
 
  Is it a known issue?
  I am worried because, as far as I understand, we're close to 1.5.2
  official
  release. Can it be worked around?
 
  Any traces which I should turn on in order to better track this issue?
  (please be precise on how to traces activation).
 
  Thanks,
  Alex
 
 
  SEVERE: error invoking
  org.apache.openejb.observer.ObserverManager$Observer@23f507cb
  java.lang.reflect.InvocationTargetException
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at
 
 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
  at
 
 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
  at java.lang.reflect.Method.invoke(Method.java:601)
  at
 
 
 org.apache.openejb.observer.ObserverManager$Observer.invoke(ObserverManager.java:145)
  at
 
 
 org.apache.openejb.observer.ObserverManager.fireEvent(ObserverManager.java:69)
  at
 
 
 org.apache.openejb.loader.SystemInstance.fireEvent(SystemInstance.java:107)
  at
 
 
 org.apache.tomee.catalina.TomcatWebAppBuilder.afterStart(TomcatWebAppBuilder.java:1491)
  at
 
 
 org.apache.tomee.catalina.GlobalListenerSupport.lifecycleEvent(GlobalListenerSupport.java:110)
  at
 
 
 org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
  at
 
 
 org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
  at
 
 
 org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:402)
  at
  org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:168)
  at
 
 
 org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
  at
  org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
  at
  org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
  at
  org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:977)
  at
 
 org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1655)
  at
  java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
  at
 java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
  at java.util.concurrent.FutureTask.run(FutureTask.java:166)
  at
 
 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
  at
 
 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
  at java.lang.Thread.run(Thread.java:722)
  Caused by: java.lang.NullPointerException
  at java.lang.String.compareTo(String.java:1139)
  at
 
 
 org.apache.openejb.server.cxf.rs.Logs$LogOperationEndpointInfo.compareTo(Logs.java:138)
  at
 
 
 org.apache.openejb.server.cxf.rs.Logs$LogOperationEndpointInfo.compareTo(Logs.java:125)
  at
 
 
 java.util.ComparableTimSort.countRunAndMakeAscending(ComparableTimSort.java:290)
  at java.util.ComparableTimSort.sort(ComparableTimSort.java:157)
  at java.util.ComparableTimSort.sort(ComparableTimSort.java:146)
  at java.util.Arrays.sort(Arrays.java:472)
  at java.util.Collections.sort(Collections.java:155)
  at
 
 
 org.apache.openejb.server.cxf.rs.CxfRsHttpListener.deployApplication(CxfRsHttpListener.java:379)
  at
 
 
 org.apache.openejb.server.rest.RESTService.deployApplication(RESTService.java:405)
  at
 
 
 org.apache.openejb.server.rest.RESTService.afterApplicationCreated(RESTService.java:241)
  at
 
 
 org.apache.tomee.webservices.TomeeJaxRsService.afterApplicationCreated(TomeeJaxRsService.java:51)
  ... 24 more
 
 

Re: TomEE 1.5.2 regression over 1.5.1: error invoking org.apache.openejb.observer.ObserverManager$Observer

[Alex The Rocker]

Hey, you're too fast :)

Questions:
1. Let me know what you changed
2. If there was a mistake in our app or in TomEE.

Indeed, somebody in my company hinted me (after I opened the JIRA) that the
faulty code could be ours, in this declaration:



1.   
@Path({tagid}http://dsxplore.dsy.ds/mashup-ui/page/xrefsearch?q=%22%7Btagid%7D%22r=V6/R2014
)

2.  @Produces({
MediaTypehttp://dsxplore.dsy.ds/mashup-ui/page/xrefsearch?q=MediaTyper=V6/R2014
.APPLICATION_XMLhttp://dsxplore.dsy.ds/mashup-ui/page/xrefsearch?q=APPLICATION_XMLr=V6/R2014
, 
MediaProviderJSONhttp://dsxplore.dsy.ds/mashup-ui/page/xrefsearch?q=MediaProviderJSONr=V6/R2014
.TYPE  http://dsxplore.dsy.ds/mashup-ui/page/xrefsearch?q=TYPEr=V6/R2014
})

3.  public 
Responsehttp://dsxplore.dsy.ds/mashup-ui/page/xrefsearch?q=Responser=V6/R2014
 getTaghttp://dsxplore.dsy.ds/mashup-ui/page/xrefsearch?q=getTagr=V6/R2014
(@Context 
HttpServletRequesthttp://dsxplore.dsy.ds/mashup-ui/page/xrefsearch?q=HttpServletRequestr=V6/R2014
 req http://dsxplore.dsy.ds/mashup-ui/page/xrefsearch?q=reqr=V6/R2014,



Is this declaration correct, or is a @GET mandatory to make it correct?

Thanks,
Alex




On Sun, Feb 17, 2013 at 9:37 PM, Romain Manni-Bucau
rmannibu...@gmail.comwrote:

 fixed

 *Romain Manni-Bucau*
 *Twitter: @rmannibucau https://twitter.com/rmannibucau*
 *Blog: **http://rmannibucau.wordpress.com/*
 http://rmannibucau.wordpress.com/
 *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
 *Github: https://github.com/rmannibucau*



 2013/2/17 Romain Manni-Bucau rmannibu...@gmail.com

  The 1.5.1 +1 snapshot renamed in 1.6.0 this week
  Le 17 févr. 2013 16:38, Alex The Rocker alex.m3...@gmail.com a
 écrit :
 
  I'm confused, what's in
 
 
 https://repository.apache.org/content/groups/snapshots/org/apache/openejb/apache-tomee/1.5.2-SNAPSHOT/if
  not 1.5.2 snapshots?
 
 
 
 
  On Sun, Feb 17, 2013 at 4:14 PM, Romain Manni-Bucau
  rmannibu...@gmail.comwrote:
 
   Subresource locator are rest services without @get, @post...it acts
 like
   proxy for other rest services.
  
   Nobody started any work on 1.5.2 so i cant say anything.
  
   Suppose we branch for 1.5.2, some rest features will not be in so i
 dint
   think you'd get this issue
   Le 17 févr. 2013 16:06, Alex The Rocker alex.m3...@gmail.com a
  écrit :
  
Romain:
   
I don't know what's subresource locator, many developers contribute
 to
   this
application (~200 .jar files in the web app!).
I have taken the time to reduce the web app to a minimum size that
   still
leads to same error at deployment time, and I have opened
https://issues.apache.org/jira/browse/TOMEE-773 JIRA.
   
I don't understand your remark about 1.5.2 (you mention it still
  doesn't
exist), can it be fixed on 1.5.2 or only on 1.6.0 ?
   
Thanks,
Alex
   
   
   
On Sun, Feb 17, 2013 at 11:46 AM, Romain Manni-Bucau
rmannibu...@gmail.comwrote:
   
 Ps: do you use subresource locator?
 Le 17 févr. 2013 10:33, Romain Manni-Bucau 
 rmannibu...@gmail.com
  a
 écrit :

  Hi
 
  First trunk is 1.6.0 snapshot (1.5.2 still doesnt exist)
 
  Then this is a small bug IMO. If you can reproduce it, it will
  help
   but
 it
  will be fixed soon normally
  Le 16 févr. 2013 23:54, Alex The Rocker alex.m3...@gmail.com
 
  a
 écrit :
 
  Hello:
 
  Our application which works fine with TomEE+ 1.5.1 miserably
  fails
   at
  startup with the following trace in catalina.out. The issue is
 so
 severe
  that it's not deployed at all.
 
  Is it a known issue?
  I am worried because, as far as I understand, we're close to
  1.5.2
  official
  release. Can it be worked around?
 
  Any traces which I should turn on in order to better track this
   issue?
  (please be precise on how to traces activation).
 
  Thanks,
  Alex
 
 
  SEVERE: error invoking
  org.apache.openejb.observer.ObserverManager$Observer@23f507cb
  java.lang.reflect.InvocationTargetException
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
  Method)
  at
 
 

   
  
 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
  at
 
 

   
  
 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
  at java.lang.reflect.Method.invoke(Method.java:601)
  at
 
 

   
  
 
 org.apache.openejb.observer.ObserverManager$Observer.invoke(ObserverManager.java:145)
  at
 
 

   
  
 
 org.apache.openejb.observer.ObserverManager.fireEvent(ObserverManager.java:69)
  at
 
 

   
  
 
 org.apache.openejb.loader.SystemInstance.fireEvent(SystemInstance.java:107)
  at
 
 

   
  
 
 org.apache.tomee.catalina.TomcatWebAppBuilder.afterStart(TomcatWebAppBuilder.java:1491

Re: TomEE 1.5.2 regression over 1.5.1: error invoking org.apache.openejb.observer.ObserverManager$Observer

[Alex The Rocker]

Nice!

Which snapshot should I use in order to test your fix ?

Alex



On Sun, Feb 17, 2013 at 10:32 PM, Romain Manni-Bucau
rmannibu...@gmail.comwrote:

 you'll see we dump more info for rest endpoints but when we did it (when I
 did it ;) i supposed @GET/@POST/... was always here which is wrong

 *Romain Manni-Bucau*
 *Twitter: @rmannibucau https://twitter.com/rmannibucau*
 *Blog: **http://rmannibucau.wordpress.com/*
 http://rmannibucau.wordpress.com/
 *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
 *Github: https://github.com/rmannibucau*



 2013/2/17 Alex The Rocker alex.m3...@gmail.com

  Hey, you're too fast :)
 
  Questions:
  1. Let me know what you changed
  2. If there was a mistake in our app or in TomEE.
 
  Indeed, somebody in my company hinted me (after I opened the JIRA) that
 the
  faulty code could be ours, in this declaration:
 
 
 
  1.   @Path({tagid}
 
 http://dsxplore.dsy.ds/mashup-ui/page/xrefsearch?q=%22%7Btagid%7D%22r=V6/R2014
  
  )
 
  2.  @Produces({
  MediaType
  http://dsxplore.dsy.ds/mashup-ui/page/xrefsearch?q=MediaTyper=V6/R2014
  .APPLICATION_XML
 
 http://dsxplore.dsy.ds/mashup-ui/page/xrefsearch?q=APPLICATION_XMLr=V6/R2014
  
  , MediaProviderJSON
 
 http://dsxplore.dsy.ds/mashup-ui/page/xrefsearch?q=MediaProviderJSONr=V6/R2014
  
  .TYPE  
 http://dsxplore.dsy.ds/mashup-ui/page/xrefsearch?q=TYPEr=V6/R2014
  
  })
 
  3.  public Response
  http://dsxplore.dsy.ds/mashup-ui/page/xrefsearch?q=Responser=V6/R2014
   getTag
  http://dsxplore.dsy.ds/mashup-ui/page/xrefsearch?q=getTagr=V6/R2014
  (@Context HttpServletRequest
 
 http://dsxplore.dsy.ds/mashup-ui/page/xrefsearch?q=HttpServletRequestr=V6/R2014
  
   req http://dsxplore.dsy.ds/mashup-ui/page/xrefsearch?q=reqr=V6/R2014
 ,
 
 
 
  Is this declaration correct, or is a @GET mandatory to make it correct?
 
  Thanks,
  Alex
 
 
 
 
  On Sun, Feb 17, 2013 at 9:37 PM, Romain Manni-Bucau
  rmannibu...@gmail.comwrote:
 
   fixed
  
   *Romain Manni-Bucau*
   *Twitter: @rmannibucau https://twitter.com/rmannibucau*
   *Blog: **http://rmannibucau.wordpress.com/*
   http://rmannibucau.wordpress.com/
   *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
   *Github: https://github.com/rmannibucau*
  
  
  
   2013/2/17 Romain Manni-Bucau rmannibu...@gmail.com
  
The 1.5.1 +1 snapshot renamed in 1.6.0 this week
Le 17 févr. 2013 16:38, Alex The Rocker alex.m3...@gmail.com a
   écrit :
   
I'm confused, what's in
   
   
  
 
 https://repository.apache.org/content/groups/snapshots/org/apache/openejb/apache-tomee/1.5.2-SNAPSHOT/if
not 1.5.2 snapshots?
   
   
   
   
On Sun, Feb 17, 2013 at 4:14 PM, Romain Manni-Bucau
rmannibu...@gmail.comwrote:
   
 Subresource locator are rest services without @get, @post...it
 acts
   like
 proxy for other rest services.

 Nobody started any work on 1.5.2 so i cant say anything.

 Suppose we branch for 1.5.2, some rest features will not be in so
 i
   dint
 think you'd get this issue
 Le 17 févr. 2013 16:06, Alex The Rocker alex.m3...@gmail.com
 a
écrit :

  Romain:
 
  I don't know what's subresource locator, many developers
  contribute
   to
 this
  application (~200 .jar files in the web app!).
  I have taken the time to reduce the web app to a minimum size
  that
 still
  leads to same error at deployment time, and I have opened
  https://issues.apache.org/jira/browse/TOMEE-773 JIRA.
 
  I don't understand your remark about 1.5.2 (you mention it still
doesn't
  exist), can it be fixed on 1.5.2 or only on 1.6.0 ?
 
  Thanks,
  Alex
 
 
 
  On Sun, Feb 17, 2013 at 11:46 AM, Romain Manni-Bucau
  rmannibu...@gmail.comwrote:
 
   Ps: do you use subresource locator?
   Le 17 févr. 2013 10:33, Romain Manni-Bucau 
   rmannibu...@gmail.com
a
   écrit :
  
Hi
   
First trunk is 1.6.0 snapshot (1.5.2 still doesnt exist)
   
Then this is a small bug IMO. If you can reproduce it, it
 will
help
 but
   it
will be fixed soon normally
Le 16 févr. 2013 23:54, Alex The Rocker 
  alex.m3...@gmail.com
   
a
   écrit :
   
Hello:
   
Our application which works fine with TomEE+ 1.5.1
 miserably
fails
 at
startup with the following trace in catalina.out. The issue
  is
   so
   severe
that it's not deployed at all.
   
Is it a known issue?
I am worried because, as far as I understand, we're close
 to
1.5.2
official
release. Can it be worked around?
   
Any traces which I should turn on in order to better track
  this
 issue?
(please be precise on how to traces activation).
   
Thanks,
Alex
   
   
SEVERE: error invoking
   
 org.apache.openejb.observer.ObserverManager$Observer@23f507cb

Command-line tools for updating TomEE configuration?

[Alex The Rocker]

Hello,

I am looking for command-line tools for modifying TomEE configuration.

I know IBM WebSphere Application Server has such tool, called
wsadmin.{sh,bat}. It allows adding JNDI aliases, JDBC datasources, etc.
even without starting the application server (if ran locally with -connType
NONE) or to a remote application server with authentication stuff.

How about TomEE, anything available?

My use case: I need to programmatically add this into tomee.xml:

Resource id=DefaultJmsResourceAdapter type=ActiveMQResourceAdapter
BrokerXmlConfig =  broker:(tcp://0.0.0.0:61617
)?useJmx=falseamp;persistent=false
ServerUrl   =  vm://localhost
Datasource  =
/Resource

Resource id=connectionFactory type=javax.jms.ConnectionFactory
ResourceAdapter = DefaultJmsResourceAdapter
/Resource

Of course it's trivial, but if there were a TomEE command-line tool for
performing this based on a scripting syntax on Administration objects
(like wsadmin works with WebSphere); then I'd use it instead of making my
own parsing  generation.

Thanks,
Alex

Re: Conflicting commons-lang*.jar in lib/ directory

[Alex The Rocker]

Okay you're right : org.apache.commons.lang and org.apache.commons.lang3

= I'll keep both commons-lang  common-lang3

Thank you very much for your quick reply !!
Alex



On Sat, Feb 9, 2013 at 10:43 AM, Romain Manni-Bucau
rmannibu...@gmail.comwrote:

 No, no conflicts (see packages)
 Le 9 févr. 2013 10:02, Alex The Rocker alex.m3...@gmail.com a écrit :

  Hello,
 
  I have written a small utility to make .jar file names in TomEE's lib/
  directory version less for the purpose of our own application upgrader
  which doesn't handles renaming (this was part of another mail thread).
 
  Thought this process, I found a strange detail : there are two different
  versions of Apache commons-lang in TomEE+ 1.5.1 lib/ directory:
 
  commons-lang-2.6.jar
  commons-lang3-3.1.jar
 
  I think it's a bug because it seems that TomEE instructs Tomcat to use in
  CLASSPATH all .jar files in lib/, and this duplicate entry can lead to
  random bugs, depending on which order the files are scanned.
 
  Do you agree it's a bug?
  Do you want me to fill a JIRA for it ?
  In the meantime, which commons-lang version should I keep ?
 
  Best regards,
  Alexandre