Re: Having 8.0.14 before christmas? Opinions?

[Wiesner, Martin]

My vote: 
+1

--
Best
Martin

> Am 06.12.2022 um 16:25 schrieb Jean-Louis Monteiro :
> 
> I'm not -1
> 
> But I'd definitely favor working on getting 9.0.0 final so we can switch to
> Jakarta EE 10 and MicroProfile 6.0
> 
> My vote: 0
> 
> Le mar. 6 déc. 2022, 16:11, Swell  a écrit :
> 
>> +1, we did not yet ship the fixes for the CVE, good to have them shipped
>> 
>> 
>> On Tue, 6 Dec 2022 at 15:47, Richard Zowalla  wrote:
>> 
>>> Hi all,
>>> 
>>> We have some dependency updates (tomcat, cxf, hsqldb) and some CVE
>>> related fixes (woodstox, shaded bcel, ...).
>>> 
>>> I was thinking about having 8.0.14 before we all get too stressed with
>>> christmas, etc. and no one has time to review / test a 8.0.14 RC.
>>> 
>>> So my questions are:
>>> 
>>> - What is the community's opionion regarding a 8.0.14 before christmas?
>>> - Are we missing any important version upgrades? Any show stoppers?
>>> 
>>> Here are the current changes in Jira
>>> 
>>> https://issues.apache.org/jira/projects/TOMEE/versions/12352390
>>> 
>>> and here is a list in plain text without the need to login:
>>> 
>>> == Dependency upgrade
>>> 
>>> [.compact]
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4100[TOMEE-4100]  X
>>> Bean 4.22
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4118[TOMEE-4118]
>>> CXF 3.4.9
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4086[TOMEE-4086]
>>> HSQLDB 2.7.1
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4107[TOMEE-4107]
>>> Jackson 2.14.0
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4116[TOMEE-4116]
>>> Tomcat 9.0.69
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4121[TOMEE-4121]
>>> Tomcat 9.0.70
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4109[TOMEE-4109]
>>> Velocity 2.3
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4110[TOMEE-4110]
>>> Woodstox 6.4.0 (CVE-2022-40152)
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4111[TOMEE-4111]
>>> bcel component
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4094[TOMEE-4094]
>>> jackson 2.14.0-rc2
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4103[TOMEE-4103]
>>> woodstox-core
>>> <
>> https://issues.apache.org/jira/browse/TOMEE-4103%5BTOMEE-4103%5Dwoodstox-core
>>> 
>>> mitigate CVE-2022-40153
>>> 
>>> == Bug
>>> 
>>> [.compact]
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4122[TOMEE-4122]
>>> Performance Regression in bean resolution in EAR files
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4101[TOMEE-4101]
>>> Typo with EL22Adaptor implementation in openwebbeans.properties
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4102[TOMEE-4102]
>>> TomEE logs SEVERE: Expected ContextBinding to have the method
>>> getThreadName()
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4014[TOMEE-4014]
>>> Unable to see TomEE version in Tomcat home page with Java 17
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4106[TOMEE-4106]
>>> TomEE version no longer appearing at default manager page
>>> 
>>> == Documentation
>>> 
>>> [.compact]
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4104[TOMEE-4104]
>>> Documentation Website: XA DataSource Configuration: Bug in MySQL Sample
>>> Code
>>> 
>>> == Fixed Common Vulnerabilities and Exposures (CVEs)
>>> 
>>> [.compact]
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4086[TOMEE-4086]
>>> HSQLDB 2.7.1
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4111[TOMEE-4111]
>>> Upgrade bcel component in TomEE
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4103[TOMEE-4103]
>>> Update woodstox-core to mitigate CVE-2022-40153
>>> 
>>> Gruß
>>> Richard
>>> 
>>> 
>> 



smime.p7s
Description: S/MIME cryptographic signature

Re: [VOTE] Apache TomEE 8.0.13 - First Attempt

[Wiesner, Martin]

Hi all,

+1 (non-binding)

Tested with several projects (primarily web services, JSF…), 
both on Linux & Mac OS, each under OpenJDK 17 (latest).

Best
Martin
—
https://twitter.com/mawiesne 


> Am 15.10.2022 um 19:41 schrieb Daniel Dias Dos Santos 
> :
> 
> Hello,
> 
> +1
> 
> On Sat, Oct 15, 2022, 14:39 Richard Zowalla  wrote:
> 
>> Any more votes?
>> 
>> Am Dienstag, dem 11.10.2022 um 19:59 +0200 schrieb Richard Zowalla:
>>> Hi all,
>>> 
>>> this is a first attempt at a vote for a release of Apache TomEE
>>> 8.0.13.
>>> 
>>> It is a maintenance release with some bug fixes and dependencies
>>> upgrades.
>>> 
>>> ###
>>> 
>>> Maven Repo:
>>> https://repository.apache.org/content/repositories/orgapachetomee-1207
>>> 
>>>  
>>>
>>>  tomee-8.0.13-release-test
>>>  Testing TomEE 8.0.13 release candidate
>>> 
>>> https://repository.apache.org/content/repositories/orgapachetomee-1207
>>> 
>>>
>>>  
>>> 
>>> ###
>>> 
>>> Binaries & Source:
>>> 
>>> https://dist.apache.org/repos/dist/dev/tomee/staging-1207/tomee-8.0.13/
>>> 
>>> ###
>>> 
>>> Tag:
>>> 
>>> https://github.com/apache/tomee/releases/tag/tomee-project-8.0.13
>>> 
>>> ###
>>> 
>>> Latest CI/CD build:
>>> 
>>> https://ci-builds.apache.org/job/Tomee/job/tomee-8.x-build-full/226/
>>> 
>>> ###
>>> 
>>> Release notes:
>>> 
>>> 
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320=12351820
>>> 
>>> ###
>>> 
>>> Here is an adoc generated version of the changelog as well:
>>> 
>>> == Dependency upgrade
>>> 
>>> [.compact]
>>> - link:https://issues.apache.org/jira/browse/TOMEE-3985[TOMEE-3985]
>>> BatchEE 1.0.2
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4057[TOMEE-4057]
>>> CXF 3.4.8
>>> - link:https://issues.apache.org/jira/browse/TOMEE-3800[TOMEE-3800]
>>> DBCP 2.9.0
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4059[TOMEE-4059]
>>> EclipseLink 2.7.11
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4063[TOMEE-4063]
>>> Geronimo Transaction Manager 3.1.5
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4019[TOMEE-4019]
>>> HSQLDB 2.7.0
>>> - link:https://issues.apache.org/jira/browse/TOMEE-3986[TOMEE-3986]
>>> Hibernate Integration 5.6.9.Final
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4042[TOMEE-4042]
>>> Jackson 2.13.4
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4067[TOMEE-4067]
>>> Jackson 2.14.0-rc1
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4020[TOMEE-4020]
>>> Jakarta Faces 2.3.18
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4026[TOMEE-4026]
>>> Johnzon 1.2.19
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4030[TOMEE-4030]
>>> Log4J2 2.18.0
>>> - link:https://issues.apache.org/jira/browse/TOMEE-3998[TOMEE-3998]
>>> MyFaces 2.3.10
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4044[TOMEE-4044]
>>> Snakeyaml 1.32
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4054[TOMEE-4054]
>>> Snakeyaml 1.33
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4002[TOMEE-4002]
>>> Tomcat 9.0.64
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4051[TOMEE-4051]
>>> Tomcat 9.0.65
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4060[TOMEE-4060]
>>> Tomcat 9.0.67
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4087[TOMEE-4087]
>>> Tomcat 9.0.68
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4018[TOMEE-4018]
>>> bcprov-jdk15on 1.70
>>> 
>>> == New Feature
>>> 
>>> [.compact]
>>> - link:https://issues.apache.org/jira/browse/TOMEE-3928[TOMEE-3928]
>>> Example for properties provider
>>> 
>>> == Bug
>>> 
>>> [.compact]
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4021[TOMEE-4021]
>>> Unexpected ehcache 3.8.1 in tomee/lib
>>> - link:https://issues.apache.org/jira/browse/TOMEE-3850[TOMEE-3850]
>>> HTTP(S) connections are not reused
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4014[TOMEE-4014]
>>> Unable to see TomEE version in Tomcat home page with Java 17
>>> - link:https://issues.apache.org/jira/browse/TOMEE-3979[TOMEE-3979]
>>> service.bat issue when using JRE_HOME on Windows
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4041[TOMEE-4041]
>>> 4
>>> CVE Vulnerabilities in snakeyaml-1.30.jar
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4001[TOMEE-4001]
>>> CVE-2022-34305 displaying user provided data without filtering,
>>> exposing a XSS vulnerability
>>> 
>>> == Improvement
>>> 
>>> [.compact]
>>> - link:https://issues.apache.org/jira/browse/TOMEE-3878[TOMEE-3878]
>>> Backport 'No interface view EJB proxies broken on JDK16+' [TOMEE-
>>> 3877] to TomEE 8.x
>>> 
>>> == Task
>>> 
>>> [.compact]
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4064[TOMEE-4064]
>>> OpenJPA 3.2.2 (examples), EclipseLink 2.7.11 (examples), Derby
>>> 10.14.2.0
>>> - link:https://issues.apache.org/jira/browse/TOMEE-4022[TOMEE-4022]
>>> Move to Apache Rat
>>> - 

Re: [DISCUSS] TomEE 8.0.13 - How do we want to deal with pending CVEs / patch versions?

[Wiesner, Martin]

Hi all,

I agree with Alex’s comments on Richard’s proposed options for the next TomEE 
8.x release. 
We should move on and ship 8.0.13 soon.

Best
Martin
—
https://twitter.com/mawiesne 


> Am 09.10.2022 um 13:11 schrieb Alex The Rocker :
> 
> Hello,
> 
> Regarding # (1): CVE-2022-42003 (jackson-databind), given that the
> only reason for having Jackson in TomEE is because of embedded TomEE;
> so the discussion here
> https://lists.apache.org/thread/ttmdc4l9z9oz9lqw3cd22sjdz451dh25 to
> replace Jackson by the Apache Johnzon (which is already part of TomEE)
> should really move on.
> Not only it is ridiculous to have two JSON processing stacks
> cohexisting in TomEE, but also, looking at
> https://mvnrepository.com/artifact/org.apache.johnzon/johnzon-core,
> there was no CVE on Johnzon for the part 5 years ; versus a huge
> number of CVE on Jackson for the same period:
> https://mvnrepository.com/artifact/com.fasterxml.jackson.core/jackson-databind
> 
> Regarding "# (2): CVE-2022-41853 (hsqldb)", I vote for solution (b)
> Add the workaround (via java args) to our startup scripts and go
> for the release , because it helps avoiding further delay at 8.0.3
> releasing, and it's better than (c) because TomEE will be "secure by
> default")
> 
> That were my 2 cents,
> Alex
> 
> Le dim. 9 oct. 2022 à 09:44, Richard Zowalla  a écrit :
>> 
>> Hi all,
>> 
>> I think, that we are soon in a good state to do a 8.0.13.
>> 
>> However, there are some open points for which I want to get the
>> community's opinion.
>> 
>> # (1): CVE-2022-42003 (jackson-databind)
>> 
>> Were is one CVE related to jackson-databind:
>> 
>> https://nvd.nist.gov/vuln/detail/CVE-2022-42003 (before 2.14.0-rc1)
>> 
>> Users are only affected, if 'UNWRAP_SINGLE_VALUE_ARRAYS' is set to
>> enabled [1]. AFAIK, we do not enable that feature by default.
>> 
>> There is an ongoing discussion about 2.14.0 final on their list but it
>> seems that it will be late October / mid November until they will
>> release that artifact.
>> 
>> Question(s) to discuss is:
>> 
>> (a) Do we want to ship a release with a RC version?
>> (b) Do we want to wait for 2.14.0.Final?
>> (c) Do we want to ship with 2.13.4 instead + adding a related section
>> to our release notes?
>> 
>> # (2): CVE-2022-41853 (hsqldb)
>> 
>> In addition, were is CVE-2022-41853, which affects HSQLDB < 2.7.1.
>> 2.7.1 isn't available yet [2]. A workaround is to set a related sytsem
>> property to mitigate the behaviour.
>> 
>> Question(s) to discuss is:
>> 
>> (a) Do we want to wait for a 2.7.1 release before doing 8.0.13 (AFAIK,
>> no ETA yet)
>> (b) Add the workaround (via java args) to our startup scripts and go
>> for the release
>> (c) Ship with 2.7.0 + adding a related section to our release notes?
>> 
>> Keep in mind: If we do not update to the "official" fix version (even
>> if we add related infos on our release note or mitigate via the
>> official workaround), automated security scanners will complain about
>> it and ops / security people will wonder about it.
>> 
>> Happy to receive feedback on these questions, so we can continue.
>> 
>> Gruß
>> Richard
>> 
>> 
>> 
>> 
>> [1]
>> https://github.com/FasterXML/jackson/discussions/126#discussioncomment-3815395
>> [2] https://github.com/advisories/GHSA-77xx-rxvh-q682
>> 
>> 
>> 
>> 



smime.p7s
Description: S/MIME cryptographic signature

Re: [DISCUSS] Renaming of master branches to main?

[Wiesner, Martin]

+1 for a transition to 'main'

—
https://twitter.com/mawiesne 


> Am 28.07.2022 um 19:20 schrieb Jean-Louis Monteiro :
> 
> Fully agree.
> 
> We should move to main
> 
> Le jeu. 28 juil. 2022, 16:54, Richard Zowalla  a écrit :
> 
>> Hi all,
>> 
>> I would like to get the community's opinion on renaming the "master"
>> branches for the TomEE related repositories to "main".
>> 
>> I see quite a few ASF projects (and other OSS projects) have made the
>> change and I personally think we should, too, for the same reason of
>> promoting inclusivity (see [1]).
>> 
>> I think we would need to update the target branch of the outstanding
>> PRs, update GitHub actions, update the Jenkins build config + local
>> checkouts. Anything else?
>> 
>> Thoughts?
>> 
>> Gruß
>> Richard
>> 
>> 
>> [1] https://sfconservancy.org/news/2020/jun/23/gitbranchname/
>> 
>> 



smime.p7s
Description: S/MIME cryptographic signature

Re: [VOTE] Apache TomEE 9.0.0-M8

[Wiesner, Martin]

+1

Best
Martin
—
https://twitter.com/mawiesne

> Am 29.06.2022 um 22:07 schrieb Jean-Louis Monteiro :
> 
> My own +1 (binding)
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
> 
> 
> On Wed, Jun 29, 2022 at 9:54 PM Cesar Hernandez 
> wrote:
> 
>> +1 thank you!
>> 
>> El mié, 29 jun 2022 a las 5:59, Daniel Dias Dos Santos (<
>> daniel.dias.analist...@gmail.com>) escribió:
>> 
>>> Hi
>>> 
>>> +1
>>> 
>>> Thanks
>>> 
>>> On Tue, Jun 28, 2022, 19:01 Jean-Louis Monteiro <
>> jlmonte...@tomitribe.com>
>>> wrote:
>>> 
 Hi,
 
 As discussed, here is the vote for Apache TomEE 9.0.0-M8. This
>> milestone
 differs from previous 9.x in the sense that we migrated all TomEE code
>> to
 the new jakarta namespace. Previously, we used bytecode relocation but
>>> most
 of the integration was broken (tests, arquillian, etc).
 
 We are still working on some regressions and fixes in order to pass all
>>> TCK
 for Jakarta EE 9.1. But starting to gather feedback can only help
>> sooner
 rather than later.
 
 This is a maintenance release with minor fixes and dependencies
>> upgrades.
 
 Maven staging repo
 
>> https://repository.apache.org/content/repositories/orgapachetomee-1205/
 
 Binaries and sources
 https://dist.apache.org/repos/dist/dev/tomee/tomee-9.0.0-M8
 
 Github Tag
 https://github.com/apache/tomee/tree/tomee-project-9.0.0-M8
 
 Commit hash
 12e5dd91fe34affa775a68d5341576b417530008
 
 Release Notes
 https://issues.apache.org/jira/projects/TOMEE/versions/12350178
 
 Sub-task
 
   - [TOMEE-3861 ] -
   Upgrade to apache-parent-26
   - [TOMEE-3865 ] -
   Switch arquillian to the new Servlet 5 protocol
   - [TOMEE-3866 ] -
   Upgrade Hibernate to 5.6.7 / Hibernate Validator to 7.0.2 (Jakarta
 Artifact)
   - [TOMEE-3868 ] -
   Remove SAAJ Axis 1 provider
   - [TOMEE-3869 ] -
   Remove JAX-RPC
   - [TOMEE-3870 ] -
   Remove Management J2EE
   - [TOMEE-3877 ] -
>>> No
   interface view EJB proxies broken on JDK16+
   - [TOMEE-3879 ] -
>>> Add
   missing --add-opens options to itests/failover
   - [TOMEE-3881 ] -
>>> Add
   JDK --add-opens to our scripts in openejb-standalone
   - [TOMEE-3920 ] -
>>> Fix
   TomEE :: Web Examples :: Moviefun Rest
   - [TOMEE-3922 ] -
   Patch Tomcat JasperInitializer and create jira
   - [TOMEE-3925 ] -
>>> Fix
   Websocket TLS Basic Auth
   - [TOMEE-3926 ] -
>>> Fix
   Webservice SSL Client Certificate Example
   - [TOMEE-3930 ] -
>>> fix
   arquillian-tomee-moviefun-example
   - [TOMEE-3931 ] -
>>> fix
   example/cucumber-jvm
   - [TOMEE-3932 ] -
   Migration tips and tricks
   - [TOMEE-3939 ] -
>>> Fix
   Jakarta Mail API with Apache Velocity Templating
   - [TOMEE-3940 ] -
>>> Fix
   TomEE :: Examples :: JakartaMail API
   - [TOMEE-3943 ] -
>>> Fix
   TomEE :: Examples :: Multiple JPA providers
   - [TOMEE-3944 ] -
>>> Fix
   TomEE :: Examples :: Simple EAR :: Functional Tests
   - [TOMEE-3953 ] -
>>> Fix
   TomEE :: Examples :: JPA with EclipseLink
   - [TOMEE-3954 ] -
>>> Fix
   TomEE :: Examples :: JPA with Hibernate and arquillian
   - [TOMEE-3956 ] -
>>> Fix
   TomEE :: Connector Examples :: Connector in WAR
   - [TOMEE-3957 ] -
>>> Fix
   TomEE :: Examples :: DeltaSpike @ConfigProperty
   - [TOMEE-3958 ] -
>>> Fix
   TomEE :: Examples :: DeltaSpike Exception Handling
   - [TOMEE-3959 ] -
>>> Fix
   TomEE :: Examples :: DeltaSpike I18n
   

Re: [VOTE] Apache TomEE 8.0.12

[Wiesner, Martin]

+1

Best
Martin
—
https://twitter.com/mawiesne


Am 14.06.2022 um 01:14 schrieb Daniel Dias Dos Santos 
mailto:daniel.dias.analist...@gmail.com>>:

+1

On Mon, Jun 13, 2022, 15:23 Richard Zowalla 
mailto:r...@apache.org>> wrote:

+1

Am Montag, dem 13.06.2022 um 12:04 -0600 schrieb Cesar Hernandez:
+1

El lun, 13 jun 2022 a las 4:57, Jonathan Gallimore (<
jonathan.gallim...@gmail.com>) escribió:

+1

Jon

On Tue, Jun 7, 2022 at 1:43 PM Jean-Louis Monteiro <
jlmonte...@tomitribe.com>
wrote:

Hi,

As discussed, here is the vote for Apache TomEE 8.0.12.

This is a maintenance release with minor fixes and dependencies
upgrades.

Maven staging repo

https://repository.apache.org/content/repositories/orgapachetomee-1203

Binaries and sources
https://dist.apache.org/repos/dist/dev/tomee/tomee-8.0.12/

Github Tag
https://github.com/apache/tomee/tree/tomee-project-8.0.12

Release Notes
https://issues.apache.org/jira/projects/TOMEE/versions/12351588

Sub-task

  - [TOMEE-3647 <
https://issues.apache.org/jira/browse/TOMEE-3647>;] -
  Update example 'mvc-resteasy' to use Server/API Bom
  - [TOMEE-3861 <
https://issues.apache.org/jira/browse/TOMEE-3861>;] -
  Upgrade to apache-parent-26

Bug

  - [TOMEE-3849 <
https://issues.apache.org/jira/browse/TOMEE-3849>;] -
  EclipseLink JPA provider not discoverable in TomEE Plume
libraries
  - [TOMEE-3903 <
https://issues.apache.org/jira/browse/TOMEE-3903>;] -
  Investigate *.tar.gz distributions aren't installed correctly
to Maven
  Repository
  - [TOMEE-3908 <
https://issues.apache.org/jira/browse/TOMEE-3908>;] -
CI
  Job für TomEE Site Publish is failing
  - [TOMEE-3919 <
https://issues.apache.org/jira/browse/TOMEE-3919>;] -
Fix
  GitHub Actions Bom Generation targeting wrong branch
  - [TOMEE-3935 <
https://issues.apache.org/jira/browse/TOMEE-3935>;] -
BOM
  Regeneration fails due to GitHub Actions permission issue
  - [TOMEE-3969 <
https://issues.apache.org/jira/browse/TOMEE-3969>;] -
  javax.cache API not part of Jakarta EE 8

Improvement

  - [TOMEE-3924 <
https://issues.apache.org/jira/browse/TOMEE-3924>;] -
  Disable @dependabot via .asf.yaml
  - [TOMEE-3934 <
https://issues.apache.org/jira/browse/TOMEE-3934>;] -
  Upgrade to Johnzon 1.2.18

Task

  - [TOMEE-3905 <
https://issues.apache.org/jira/browse/TOMEE-3905>;] -
Fix
  Post release pom versioning for tomee-8.x branch

Dependency upgrade

  - [TOMEE-3911 <
https://issues.apache.org/jira/browse/TOMEE-3911>;] -
  Upgrade XBean to 4.21
  - [TOMEE-3912 <
https://issues.apache.org/jira/browse/TOMEE-3912>;] -
  Upgrade TomEE Patch Plugin to 0.9
  - [TOMEE-3913 <
https://issues.apache.org/jira/browse/TOMEE-3913>;] -
  Examples: Upgrade JUnit 4.12 to 4.13.2
  - [TOMEE-3918 <
https://issues.apache.org/jira/browse/TOMEE-3918>;] -
  Upgrade Johnzon to 1.2.17
  - [TOMEE-3941 <
https://issues.apache.org/jira/browse/TOMEE-3941>;] -
  Apache ActiveMQ 5.16.5
  - [TOMEE-3961 <
https://issues.apache.org/jira/browse/TOMEE-3961>;] -
  Upgrade to Apache Tomcat 9.0.63 (CVE-2022-29885)
  - [TOMEE-3977 <
https://issues.apache.org/jira/browse/TOMEE-3977>;] -
  Apache OpenWebBeans 2.0.27

Documentation

  - [TOMEE-3846 <
https://issues.apache.org/jira/browse/TOMEE-3846>;] -
  Inconsistence between tomee flavors comparison in website and
actual
jars
  - [TOMEE-3904 <
https://issues.apache.org/jira/browse/TOMEE-3904>;] -
  Enhance / Update existing release documentation


Please VOTE

[+1] go ship it
[+0] meh, don't care
[-1] stop, there is a ${showstopper}

The VOTE is open for 72h

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com

Re: TomEE 9.x - from javax to jakarta namespace

[Wiesner, Martin]

+1

Best
Martin
—
https://twitter.com/mawiesne


Am 11.05.2022 um 19:00 schrieb Cesar Hernandez 
mailto:cesargu...@gmail.com>>:

+1, Thank you!


El mié, 11 may 2022 a las 9:06, Daniel Dias Dos Santos (<
daniel.dias.analist...@gmail.com>) 
escribió:

+1

On Wed, May 11, 2022, 12:00 Zowalla, Richard <
richard.zowa...@hs-heilbronn.de> wrote:

I am fine with it: +1

Von: Jean-Louis Monteiro 
mailto:jlmonte...@tomitribe.com>>
Gesendet: Mittwoch, 11. Mai 2022 15:57:54
An: dev@tomee.apache.org
Betreff: Re: TomEE 9.x - from javax to jakarta namespace

Alright, with the latest changes pushed yesterday and today, we are now
at
the exact same numbers for TomEE 8.x / Jakarta EE 8 under JDK8 and TomEE
9.x / Jakarta 9.1 under JDK17.

If everyone is ok with it, we can create a new milestone and give users
the
opportunity to provide us with some feedback and to report bugs.

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Tue, May 10, 2022 at 7:06 PM David Blevins 
wrote:

Was checking out the TCK numbers this morning can make to suggest a
9.0.0-M8 while things look good and found this amazing email.

The 9.0.x branch is looking absolutely amazing!!!

What do we think about pushing out a 9.0.0-M8 while things are in their
peak-stable state?  I'm sure we'll have to rip up a few more things to
finish off the remaining Jakarta EE and MP TCK issues.  Would be great
to
have something that isn't M7 to fallback on as a reference point to
track
regressions.

Thoughts?


-David



On May 10, 2022, at 3:56 AM, Jean-Louis Monteiro <
jlmonte...@tomitribe.com> wrote:

Hi all,

Time for some reporting

On our journey to migrate TomEE over from javax to jakarta namespace,
we
had many issues.
After updating all our code, we had to do a bunch of dependency
upgrades
after upgrading many of them (OpenWebbeans, BVal, Geronimo, etc).

We then faced many issues with non compatible libraries for example
(ActiveMQ, commons-dbcp, CXF, sxc, taglib, etc). So we ended up
repacking
them in our own groupId after using the Maven Shade plugin to
relocate
the
packages.

We worked on BVal TCK and CDI TCK and we are close to passing them.

But we had before to solve all our outdated MicroProfile 1.3 stack to
the
most recent and jakarta compatible version. Geronimo implementations
being
far being, we decided to use some SmallRye implementations until we
can
dedicate some time to update our Apache implementations (config,
metrics,
health, openapi, opentracing, fault tolerance).

Our build is now more stable, but still not green. Some issues are
basically easy to fix and most people could do it (examples for
instance).

https://ci-builds.apache.org/job/Tomee/job/master-build-full/

The integration for openapi, opentracing and fault tolerance is not
done
and we are far from passing the TCK. On config, metrics and health we
are
close. Same for our JWT implementation.

I also wanted to have a view on the platform TCK, so I decided to
stop
TomEE work in order to spend time on the Platform TCK to do all
dependency
upgrades and get the TCK to run properly. I'm pleased to announce
that
after 2 weeks of hard work, we are 99% compatible

https://tck.work/tomee/build?id=1652104572445

Thanks everyone for the help.
Keep going and if you need some guidance or help, let us know.

For coordination purposes, here is the issue
https://issues.apache.org/jira/browse/TOMEE-3862
Many subtasks are there and you can create new tasks when needed and
ask
any committer to assign it to you.



--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Thu, May 5, 2022 at 11:13 AM Zowalla, Richard <
richard.zowa...@hs-heilbronn.de> wrote:

Yes - we already yanked it in 9.x

Gruß
Richard

Am Donnerstag, dem 05.05.2022 um 10:10 +0100 schrieb Jonathan
Gallimore:
Sounds good. I'll drop the transformer from the 8.x branch (looks
like we
don't use it in 9.x), and I'll create a single example to
demonstrate
it in
a sandbox.

Jon

On Wed, May 4, 2022 at 12:32 PM Zowalla, Richard <
richard.zowa...@hs-heilbronn.de> wrote:

You are right - we can remove it imho from 8.x as we do not test
with
it and the transformed samples might not even work, e.g.
dependencies
are not migrated, etc.

+1 for providing a (bigger) example.

Gruß
Richard

Am Mittwoch, dem 04.05.2022 um 11:17 +0100 schrieb Jonathan
Gallimore:
I've picked up a task related to the examples:
https://issues.apache.org/jira/browse/TOMEE-3873. I specifically
went
for
this, as I added the Eclipse Transformer to the build for a
number of
examples in the past, back when we were doing the transformation
process on
TomEE itself. The drawbacks here is that any tests in the
examples
run on
the javax code, and we just "assume" that the transformed
artifact
works. I

Re: [VOTE] Apache TomEE 8.0.11 - take 2

[Wiesner, Martin]

+1

Thanks to all contributors of this release.

Best
Martin
—
https://twitter.com/mawiesne


Am 21.04.2022 um 14:28 schrieb Jonathan Gallimore 
mailto:jonathan.gallim...@gmail.com>>:

+1

Thanks Richard and Jean-Louis!

Jon

On Thu, Apr 14, 2022 at 4:06 PM Jean-Louis Monteiro <
jlmonte...@tomitribe.com> wrote:

Hi All,

This is the first attempt at a vote for a release of Apache TomEE 8.0.11

I'd like to start with a big thank you and a big applause to Richard. He
has been doing a tremendous work on the project and started to roll out his
first release today. Per Apache rules, the release manager needs to be a
TomEE PMC, that's why I'm starting this VOTE, but the work has been done by
Richard, so thank you. Well done.

Maven Repo:
https://repository.apache.org/content/repositories/orgapachetomee-1200/

Binaries & Sources:
https://dist.apache.org/repos/dist/dev/tomee/staging-1200/tomee-8.0.11/

Tags:
https://github.com/apache/tomee/releases/tag/tomee-project-8.0.11

Release notes:

https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320=12351352

Here are the releases notes
Bug

  - [TOMEE-3840 ] -
  TomEE WebProfile 8.0.9 does not start with security enabled
  - [TOMEE-3848 ] -
  Apache TomEE 8.0.6 onwards is packaged with quartz-2.2.4.jar
  - [TOMEE-3860 ] -
  Upgrade jackson-databind for CVE-2020-36518
  - [TOMEE-3871 ] -
  TomEE Plume is missing BatchEE / JCS Cache
  - [TOMEE-3876 ] - BOM
  generation corrupted under windows (slash problems)
  - [TOMEE-3889 ] -
  Invalid ObjectName for MDB listening to wildcard destination
  - [TOMEE-3892 ] -
  TomEE Maven Plugin does not allow to override default "-ea" in
RemoteServer

Improvement

  - [TOMEE-3842 ] -
  GitHub Actions fails for PullRequest Builds due to BOM auto generation
  - [TOMEE-3851 ] -
  Replace Google Analytics with ASF Matomo
  - [TOMEE-3859 ] -
  Update tomee.xml file so it refers to the right location

Task

  - [TOMEE-3852 ] -
  Review the website in regard to external embedding of resources (JS,
Fonts,
  CSS)
  - [TOMEE-3853 ] -
Link
  ASF Privacy Policy from TomEE Website

Dependency upgrade

  - [TOMEE-3841 ] -
  Upgrade SLF4J to 1.7.36
  - [TOMEE-3845 ] -
  Upgrade Tomcat to 9.0.59
  - [TOMEE-3855 ] -
  Upgrade Tomcat to 9.0.60
  - [TOMEE-3856 ] -
  Upgrade to jackson 2.13.2
  - [TOMEE-3858 ] -
  Upgrade OpenJPA to 3.2.2
  - [TOMEE-3872 ] -
  Update Hibernate Integration to 5.6.7
  - [TOMEE-3886 ] -
  Upgrade tomcat to 9.0.62
  - [TOMEE-3893 ] -
  Upgrade to jackson 2.13.2.2

Documentation

  - [TOMEE-3814 ] -
  Commented SSL Connector fix for tomee server.xml
  - [TOMEE-3846 ] -
  Inconsistence between tomee flavors comparison in website and actual
jars
  - [TOMEE-3847 ] -
  Exception when building website from windows os
  - [TOMEE-3854 ] -
  Provide a first draft of a link collection page targeting
  contributor/committer resources
  - [TOMEE-3888 ] -
  Cleanup documentation
  - [TOMEE-3894 ] -
  website generation broken under windows


(Developers - please review and adjust your tickets if necessary!)

Please VOTE:

[+1] Yes, release it
[+0] Not fussed
[-1] Don't release, there's a showstopper (please specify what the
showstopper is)

Vote will be open for 72 hours.

Thanks
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com

Re: [VOTE] Apache TomEE 8.0.10

[Wiesner, Martin]

Hi All,

+1

Conducted my tests as usual with J17 / MacOS.

Best
Martin
--
https://twitter.com/mawiesne


Am 15.02.2022 um 15:18 schrieb Jonathan Gallimore 
mailto:jonathan.gallim...@gmail.com>>:

+1

Jon

On Fri, Feb 11, 2022 at 8:54 AM Jean-Louis Monteiro <
jlmonte...@tomitribe.com> wrote:

Hi All,

This is a first attempt at a vote for a release of Apache TomEE 8.0.10

Maven Repo:
https://repository.apache.org/content/repositories/orgapachetomee-1193/

Binaries & Source:
https://dist.apache.org/repos/dist/dev/tomee/staging_1193-TomEE-8.0.10/

Tags:
https://github.com/apache/tomee/releases/tag/tomee-project-8.0.10

Release notes:

https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320=12350706

Here are the releases notes
Sub-task

  - [TOMEE-2117 ] -
  Rework ProcessObserverMethod integration
  - [TOMEE-2289 ] -
  MicroProfile OpenAPI Example
  - [TOMEE-2349 ] -
  Ensure each module can generate javadoc jars on release
  - [TOMEE-2350 ] -
  Create a list of existing Javadoc using html
  - [TOMEE-2351 ] -
  MicroProfile OpenTracing Example for Distributed Microservices
  - [TOMEE-2358 ] -
  MicroProfile JWT rest-mp-jwt-claim Example

Bug

  - [TOMEE-2169 ] -
  Interceptor Bean injection does not work for EJBs
  - [TOMEE-2270 ] -
  Java11: Unable to initialize agent with embedded-maven-plugin
  - [TOMEE-2403 ] -
  AutoConnectionTrackerTest fails randomly
  - [TOMEE-2427 ] -
  Align text above the pictures
  - [TOMEE-2800 ] -
  Issue : Unable to run EJB test cases for upgradation in current project
  with Java 1.8 and WebLogic version 12.2.1.4 along with
openejb.cxf.version
  7.0.1 / openejb.cxf.version 8 jar.
  - [TOMEE-2941 ] -
  Regression: A connection factory created with TransactionSupport of
"none"
  only sending message when transaction completes
  - [TOMEE-3777 ] -
  
  org.apache.openjpa.persistence.ArgumentException: The persistence
provider
  is attempting to use properties in the persistence.xml file to resolve
the
  data source ...
  - [TOMEE-3816 ] -
  Return "this" on stateless EJB method looses container transaction
  management
  - [TOMEE-3823 ] -
  TomEE and Java 17 compatibility issue with Windows Service Tooling
  - [TOMEE-3825 ] -
  TomEE Maven Plugin does not wait for container startup, if
"checkStarted"
  is set to true
  - [TOMEE-3832 ] -
  JAX-RS TomEEJsonbProvider not registered in tomee-embedded-maven-plugin
  when MicroProfile is present

New Feature

  - [TOMEE-2306 ] - New
  Java EE Schemas for Java EE Deployment Descriptors
  - [TOMEE-2584 ] -
Java
  11 compliancy
  - [TOMEE-2706 ] - New
  TomEE Embedded Bootstrap

Improvement

  - [TOMEE-1618 ] -
  Replace three register maps in Container in favour of one
  - [TOMEE-2277 ] -
  Java11: module name for TomEE
  - [TOMEE-2425 ] -
  Generate TomEE-Cluster.html page
  - [TOMEE-2519 ] - MP
  JWT Logging Improvements
  - [TOMEE-2847 ] -
  Patch key `jakarta` namespace support
  - [TOMEE-2949 ] -
  Match TomEE tar and zip file syntax with extracted folder
  - [TOMEE-3826 ] - Add
  exclusion list maven config for patch plugin to preserve jars with
signature

Wish

  - [TOMEE-2347 ] - Use
  Asciidoc for all Javadoc

Task

  - [TOMEE-2285 ] -
  Microprofile Examples
  - [TOMEE-2867 ] - Add
  Documentation links to website download page
  - [TOMEE-2868 ] - Add
  instructions on each example page
  - [TOMEE-3724 ] -
 

Re: Uprade to latest Johnzon+OpenJPA+OWB - New TomEE release?

[Wiesner, Martin]

Hi all,

release of version 8.0.10 would be a fine, as brought up by Thomas.
Maintenance branch for 8.x could be opened once these dep updates are included.

Is there anything else pending for inclusion into 8.0.10?

Best
Martin
—
https://twitter.com/mawiesne

Am 08.02.2022 um 16:02 schrieb Thomas Andraschko 
mailto:andraschko.tho...@gmail.com>>:

great, thanks!

Am Di., 8. Feb. 2022 um 15:56 Uhr schrieb Zowalla, Richard <
richard.zowa...@hs-heilbronn.de>:

Sounds great to have a new release of TomEE soon.

Am Dienstag, dem 08.02.2022 um 15:51 +0100 schrieb Jean-Louis Monteiro:
I have done all the updates this morning already.

The short version of the build is green
https://ci-builds.apache.org/job/Tomee/job/master-build-quick/228/
The complete version is still pending
https://ci-builds.apache.org/job/Tomee/job/master-build-full/475/

After that I don't see why we would not be able to release and switch
after
that to 9.x

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Tue, Feb 8, 2022 at 3:44 PM Thomas Andraschko <
andraschko.tho...@gmail.com> wrote:

Hi,

Romain released new versions of those 3 libs - and i would need the
upgrade
of Johnzon (polymorphic issues) and OpenJPA (@AttributeConverter
support).
Would it be possible to upgrade those and release a new version?
Would be
very great.

I can provide a PR for those updates.

Best regards,
Thomas

Re: Move TomEE master to 9.x for EE 9 and onward

[Wiesner, Martin]

Hi all,

+1 to proceed as proposed by Jean-Louis.

Best
Martin
—
https://twitter.com/mawiesne


Am 08.02.2022 um 09:22 schrieb Thomas Andraschko 
mailto:andraschko.tho...@gmail.com>>:

+1 to move on

i would also like to get another 8.0.x release but i will send another mail
soon :)

Am Di., 8. Feb. 2022 um 08:07 Uhr schrieb Zowalla, Richard <
richard.zowa...@hs-heilbronn.de>:

Hi all,

I am strongly +1 for moving forward with it, i.e. time to move on with
master.

There is definitley the need for some artifacts (arquillian, app
composer), which are not covered by the byte-code approach and which
are required to migrate (fully w/o byte code transformation) to the
jakarta namespace :)

Although - I think it is clear to everyone - the 8.x branch will
(obviously) stay for a couple of years as it is the last javax
namespace supporting release.

Gruß
Richard


Am Dienstag, dem 08.02.2022 um 00:04 +0100 schrieb Jean-Louis Monteiro:
Hi all,

We have discussed it a couple of times here and there. I'd like to
open a
dedicated thread for it.

EE 9 has been released and we have created a TomEE 9.x milestone to
pass
the TCK. The approach to do bytecode changes to support javax ->
jakarta
namespace changes proved to work but it's also been more complex than
expected. We have a limited fork with limited features. We don't
support
nearly as much as we do in the 8.x branch.

The goal was to decrease the maintenance cost for the community, but
in
reality I fear we are on the opposite path.

I'd like to create a TomEE 8.x maintenance branch where we keep
fixing
stuff, upgrading libraries and do as many releases as possible and as
long
as we can to support javax namespace. I know it's the last compatible
version so the topic is not when TomEE is going to be EOL.

But if we do that, we could move master to TomEE 9 and start merging
back
all changes we did in the fork and finally create an EE 9 final
release.

EE 10 is around the corner, if we want to keep supporting EE and
being
certified, we need to avoid big jumps.

What does the community think?

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com

Re: TomEE Jakarta project - have we reach the limit?

[Wiesner, Martin]

Hi all,

the proposed plan by Thomas sounds reasonable. +1

IMHO, 8.0.x line should definitely be continued for those not able to migrate 
yet, as brought up by Jean-Louis.
Given the planned 8.0.9 version will compatible and work with Java 17 (LTS), 
that 8.0.x line should be curated for some time.

That’s my 2c.

Best
Martin
—
http://twitter.com/mawiesne


Am 05.10.2021 um 12:17 schrieb Jean-Louis Monteiro 
mailto:jlmonte...@tomitribe.com>>:

Thanks for the additional thoughts Thomas.

I'll wait for some more thoughts and I might create a poll and let everyone
to vote on what they like.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Tue, Oct 5, 2021 at 10:59 AM Thomas Andraschko <
andraschko.tho...@gmail.com> wrote:

yep
i think we have to maintain 8.0.x anyway as its the last javax release and
we cant expect that everyone does a fast migration

IMO the following is the best way:
- branch 8.0.x
- make master 9.0 and rename javax -> jakarta
- branch 9.0 after everything is working fine
- working on 10.0 in master
- maintain 8.0 and 10.0 and dont maintain the 9.0 branch


Am Di., 5. Okt. 2021 um 10:53 Uhr schrieb Jean-Louis Monteiro <
jlmonte...@tomitribe.com>:

Agreed ...

1.7.x - EOL
7.0.x and 7.1.x - mostly similar so if we maintain one, we should
maintain
the other.

But I agree that 1 actively developed version (TomEE master/TomEE 9.x)
and
1 maintained version (TomEE 8.x) is good.
That'd be my choice.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Tue, Oct 5, 2021 at 10:37 AM Zowalla, Richard <
richard.zowa...@hs-heilbronn.de> wrote:

+1

I am wondering, if we still maintain 7.0.x, 7.1.x in the future (1.7.x
is eol, I guess) ? Maintenance cost will rise with every additional
version branch. The last releases of 7.0.x and 7.1.x are 1 year old...
but this is maybe another discussion.


Am Dienstag, dem 05.10.2021 um 10:05 +0200 schrieb Jean-Louis Monteiro:
Thanks everyone.

Same feeling here.
I think we tried and pushed it as much as we could.

What we can do is make sure we fix remaining failures on TCK and
support
JDK 17 with TomEE.
Do a release, branch for maintenance and move master to jakarta.

Does it sound like an acceptable plan?

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Tue, Oct 5, 2021 at 7:56 AM David Jencks <
david.a.jen...@gmail.com

wrote:

Maybe even “Our second release _confirmed_…”…

David Jencks

On Oct 4, 2021, at 12:33 PM, David Blevins <
david.blev...@gmail.com>
wrote:
- Our first release proved releasing both 8 & 9 together can be
impractical.  The TomEE 8 binaries were a dud, only TomEE 9 was
released.
There was communication overhead and made for a potentially
confusing
release.  The TomEE 9 binaries are still very limited.
- Our first release proved releasing both 8 & 9 together can be
impractical.  The TomEE 8 binaries were released, we didn't release
TomEE
9.  It's the second time we've done that.  We've only managed one
TomEE 9
release in the last 10 months.
This was supposed to start "our second
release".  CopyPasteException :)

-David

--
Richard Zowalla, M.Sc.
Research Associate, PhD Student | Medical Informatics

Hochschule Heilbronn – University of Applied Sciences
Max-Planck-Str. 39
D-74081 Heilbronn
phone: +49 7131 504 6791 (zur Zeit nicht via Telefon erreichbar)
mail: richard.zowa...@hs-heilbronn.de
web: https://www.mi.hs-heilbronn.de/

Re: [VOTE] Apache TomEE 8.0.8

[Wiesner, Martin]

Hi all,

+1 (non-binding)

Tested in several projects (primarily web services, JAXB, REST…),
both on Linux & Mac OS, each under AdoptOpenJDK 11 (latest).

Best
Martin
—
https://twitter.com/mawiesne

Am 06.09.2021 um 10:27 schrieb Jean-Louis Monteiro 
mailto:jlmonte...@tomitribe.com>>:

+1 (binding)
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Thu, Sep 2, 2021 at 5:31 PM Alex The Rocker  wrote:

Alright so my vote is [+1] non-binding for TomEE 8.0.8 based on my
tests (I doubt the fix for activemq exception can be in time for
8.0.8, let's keep this one for 8.0.9...)

Alex

Le jeu. 2 sept. 2021 à 17:23, Jean-Louis Monteiro
 a écrit :

The change has been introduced in Java version 16+

See https://openjdk.java.net/jeps/396
and https://bugs.openjdk.java.net/browse/JDK-8256358

JEP 396: Strongly Encapsulate JDK Internals by Default (JDK-8256299
) core-libs

Strongly encapsulate all internal elements of the JDK by default,
except
for critical internal APIs <
https://openjdk.java.net/jeps/260#Description>
such as sun.misc.Unsafe. Allow end users to choose the relaxed strong
encapsulation that has been the default since JDK 9.

With this change, the default value of the launcher option
--illegal-access
 is
now
deny rather than permit. As a consequence, existing code that uses most
internal classes, methods, or fields of the JDK will fail to run. Such
code
can be made to run on JDK 16 by specifying --illegal-access=permit.
That
option will, however, be removed in a future release.

For further details, please see JEP 396
.


You need to add --illegal-access=permit to your surefire configuration or
add it to your JVM options.

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Thu, Sep 2, 2021 at 2:57 PM Alex The Rocker 
wrote:

Hello again,

Of course my vote related to TomEE 8.0.8 experiments with Java 16 is
not blocking the release since it's not a binding vote.
I continued my tests and I found no regression with TomEE+ 8.0.8 with
IBM Semeru Runtime 11.0.12 (new name for AdoptOpenJDK OpenJ9) with a
app which relies on JAX-WS / JAX-RS / JMS & Websockets.

With Java 16 runtime, I have this annoying exception in catalina.out
when I use the embedded ActiveMQ for JMS purposes:

02-Sep-2021 12:50:33.955 SEVERE [ActiveMQ Task-1]
org.apache.activemq.util.IntrospectionSupport.setProperty Could not
set property host on Socket[unconnected]
java.lang.reflect.InaccessibleObjectException: Unable to make public
void sun.security.ssl.SSLSocketImpl.setHost(java.lang.String)
accessible: module java.base does not "export
sun.security.ssl" to unnamed module @8960bcc0
at

java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:357)
at

java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
at

java.base/java.lang.reflect.Method.checkCanSetAccessible(Method.java:199)
at java.base/java.lang.reflect.Method.setAccessible(Method.java:193)
at

org.apache.activemq.util.IntrospectionSupport.setProperty(IntrospectionSupport.java:179)
at

org.apache.activemq.util.IntrospectionSupport.setProperties(IntrospectionSupport.java:155)
at

org.apache.activemq.util.IntrospectionSupport.setProperties(IntrospectionSupport.java:140)
at

org.apache.activemq.transport.tcp.SslTransport.(SslTransport.java:81)
at

org.apache.activemq.transport.tcp.SslTransportFactory.createTransport(SslTransportFactory.java:122)
at

org.apache.activemq.transport.TransportFactory.doCompositeConnect(TransportFactory.java:138)
at

org.apache.activemq.transport.TransportFactory.compositeConnect(TransportFactory.java:91)
at

org.apache.activemq.transport.failover.FailoverTransport.doReconnect(FailoverTransport.java:1013)
at

org.apache.activemq.transport.failover.FailoverTransport$2.iterate(FailoverTransport.java:149)
at

org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:133)
at

org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:48)
at

java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
at

java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630)
at java.base/java.lang.Thread.run(Thread.java:883)

It's not blocking the JMS requests from executing.

Bbut accumulating exceptions in logs is not something we appreciate,
since we have alerters on exceptions rates in production, so I hope
that issue (which is not new with TomEE+ 8.0.8, same issue with 8.0.6)
will soon be fixed, again having in mind that Java 17 LTS availability
is getting close...

Hope it helps,
Alex

Le jeu. 2 sept. 2021 à 09:57, Thomas Andraschko
 a écrit :

+1 (non-binding)

I think we should work on java17 after that release

Alex The Rocker  schrieb am Do., 2. Sept.
2021,
09:52:

Hello,

[-1] (non 

Re: [DISCUSS] Release Apache TomEE 8.0.7 and 9.0.0-M7

[Wiesner, Martin]

+1 for David's proposed strategy how to handle the identified regression. That 
should prevent many surprises for 8.0.x users in the community which was my 
main concern why I voted a „0“ this time.

I’m optimistic that an upcoming 8.0.8 release will shine again. I can provide 
feedback once 8.0.8 staging binaries are available and a vote is open, or via a 
virtual coffee with Richard (Z).

Best
Martin
-
https://twitter.com/mawiesne


Am 03.05.2021 um 22:30 schrieb David Blevins 
mailto:david.blev...@gmail.com>>:

Launching off a discuss thread so we can track issues and discuss without 
filling up the vote thread.

Sounds like there are regressions on the 8.0.7.  What I'd recommend is we just 
don't put 8.0.7 on the mirror system or website.  We leave the mirrors and 
website with 8.0.6 until there are better 8.0.x binaries available and just put 
up the 9.x binaries.

Tomcat does this fairly often if there's a bad build of one of the branches.  
If you look here there are 36 releases of 9.x, but the highest version number 
is 9.0.45, so a decent percentage were never published:

- http://archive.apache.org/dist/tomcat/tomcat-9/

I think that's probably one of the reasons they can crank out so many releases 
so consistently despite maintaining 3 branches.

Thoughts?


-David

Re: [VOTE] Release Apache TomEE 8.0.7 and 9.0.0-M7

[Wiesner, Martin]

Hi all,

after quick review and discussion with Richard Z, we found JAX-RS is _not_ 
working out of the box for 8.0.7.
Reasons: see Richard’s comment below.

For the aforementioned reason, but with strategic goals in mind, my 
(non-binding) vote is:
-0

Best
Martin
—
https://twitter.com/mawiesne


Am 03.05.2021 um 18:13 schrieb Zowalla, Richard 
mailto:richard.zowa...@hs-heilbronn.de>>:

Seems, that "application/json" support via JAX-RS is broken for 8.0.7
[1]. We should fix this in 8.0.8 asap otherwise 8.0.7 is unusable for
us.

Basically, it is the same issue our unit tests experience in "openejb-
cxf-rs" [2].

For the sake of getting certified _and_ meeting the deadline, I am
going to vote +0

Gruss
Richard



[1] https://gist.github.com/rzo1/a9ca1f5e7765fe4986ad86c44bc93813
[2]
https://ci-builds.apache.org/job/Tomee/job/master-build-quick/118/org.apache.tomee$openejb-cxf-rs/

Am Montag, den 03.05.2021, 12:30 -0300 schrieb Daniel Dias Dos Santos:
Hello +1

Thanks

On Mon, May 3, 2021, 12:01 David Blevins 
wrote:

Ok, folks,

Here we go.  Again, bear in mind we need these binaries for the
Jakarta EE
9.1 release ballot today.  Any issues and we can roll a Apache
TomEE 8.0.8
and Apache TomEE 9.0.0-M8 asap.  I think we should plan on doing
that
anyway, so feel free to say call it straight out when reporting "I
found x
issue we should fix in 8.0.8"


TomEE Patch Plugin v0.5
https://repository.apache.org/content/repositories/orgapachetomee-1182/

Apache TomEE 8.0.7
https://repository.apache.org/content/repositories/orgapachetomee-1183/

Apache TomEE 9.0.0-M7
https://repository.apache.org/content/repositories/orgapachetomee-1184/

This vote will be open for 72 hours.  Please vote +1, 0, -1.  When
voting
-1, please state the reason.



--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com

Re: Potential release vote for 8.0.7 and 9.0.0-M7

[Wiesner, Martin]

Hello all, hello (tired) David

I'm in favor of rolling a release (vote). Here's my „+1“.

Thx in advance to all contributors who made this great progress possible!

Best
Martin
—
https://twitter.com/mawiesne


Am 01.05.2021 um 17:01 schrieb Daniel Dias Dos Santos 
mailto:daniel.dias.analist...@gmail.com>>:

Hello David,

I am in favor of releasing the vote, here's my +1


Em sex., 30 de abr. de 2021 às 22:32, David Blevins 
mailto:david.blev...@gmail.com>>
escreveu:

Heads up that we are narrowing in in the last few TCK issues and there is
still some chance we can be Jakarta EE 9.1 Web Profile certified in time
for the Jakarta EE 9.1 release vote Monday.

It would be super super and I mean *super* tight

However, if we can get it done we'll need to do a release vote by no later
than Sunday afternoon and file our certification request.  We don't need to
have concluded our vote to make the Jakarta EE 9.1 release ballot, we just
need final binaries of our own to be at least in staging and in the process
of our own vote.

We do need that vote pass, however, so that would require some pragmatism
on all our parts.

For that reason I recommend we do not try to push out a 9.0.0 final, but
go ahead with 9.0.0-M7. If there are some issues with the binaries we put
up for vote, unless they are legal issues, we can still release them and
immediately fix the issues next week in a subsequent 8.0.8 and 9.0.0-M8.
There's no reason to "wait", we can simply release twice.  Version numbers
are free.

The Jakarta EE 9.1 release vote lasts for two weeks and an announcement
would happen some days after that.  Ff we did want to push out a 9.0.0 for
the announcement, we'd have at least till May 17th to do that, perhaps even
the 20th.

The reason we want to get certified in time for the ballot is recently
there was a change that implementations listed on the ballot get a special
place at the top of the specification page.  Any implementations that come
even one day later cannot be included and will not be accepted or given
special designation.  This lasts forever and is a permanent advantage to
those in the list.  It's also a permanent *disadvantage* to those not on
the list.  It's eat or be eaten.

So that's what we're going for:  A staged binary up for a vote here,
passing the TCK, in time to be listed on the Jakarta EE 9.1 release ballot
Monday.


-David

Re: [VOTE] Release Apache TomEE 8.0.6

[Wiesner, Martin]

Hi all,

here’s my 

+1 (non-binding) => for TomEE 8.0.6 

Tested with several projects (primarily web services, JAXB, REST…), 
both on Linux & Mac OS, each under AdoptOpenJDK 11 (latest, 11.0.9.1). 
=> no show stoppers found.

Best
Martin
—
https://twitter.com/mawiesne 

> Am 14.01.2021 um 23:55 schrieb Daniel Dias Dos Santos 
> :
> 
> ±1
> 
> On Thu, Jan 14, 2021, 18:47 Cesar Hernandez  wrote:
> 
>> +1 (plus one)
>> 
>> El jue, 14 ene 2021 a las 13:17, Zowalla, Richard (<
>> richard.zowa...@hs-heilbronn.de>) escribió:
>> 
>>> Hi,
>>> 
>>> +1 from my side.
>>> 
>>> I tested the 8.0.6 plus artifact with our fullstack EAR app.
>>> 
>>> Thanks, John for your time / work in preparing this release artifact :)
>>> 
>>> Gruss
>>> Richard
>>> 
>>> Am Donnerstag, den 14.01.2021, 16:05 + schrieb Jonathan Gallimore:
 Hi All,
 
 This is a first attempt at a vote for a release of Apache TomEE
 8.0.6.
 
 Maven Repo:
 
>>> https://repository.apache.org/content/repositories/orgapachetomee-1179
 
 Binaries & Source:
 
>>> https://dist.apache.org/repos/dist/dev/tomee/staging-1179/tomee-8.0.6/
 
 Source code:
 
>>> 
>>> 
>> https://dist.apache.org/repos/dist/dev/tomee/staging-1179/tomee-8.0.6/tomee-project-8.0.6-source-release.zip
 
 Tags:
 
>>> 
>>> 
>> https://gitbox.apache.org/repos/asf?p=tomee.git;a=tag;h=refs/tags/tomee-8.0.6
 
 Release notes:
 
 
>>> 
>>> 
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320=12349403
 
 (Developers - please review and adjust your tickets if necessary!)
 
 Please VOTE:
 
 [+1] Yes, release it
 [+0] Not fussed
 [-1] Don't release, there's a showstopper (please specify what the
 showstopper is)
 
 Vote will be open for 72 hours.
 
 Thanks
 
 Jon
>>> 
>> 
>> 
>> --
>> Atentamente:
>> César Hernández.
>> 

--
Dipl.-Inform. Med. Martin Wiesner
Research Associate





Hochschule Heilbronn – University of Applied Sciences
Max-Planck-Str. 39 
D-74081 Heilbronn 

phone: +49 (0)7131 - 504 1124 bzw. 504 6947 
fax: +49 (0)7131 - 252 470 
mail: martin.wies...@hs-heilbronn.de  
web: http://www.mi.hs-heilbronn.de/ 

GMDS-AG Consumer Health Informatics
web: 
https://gmds.de/aktivitaeten/medizinische-informatik/arbeitsgruppenseiten/consumer-health-informatics-chi
 






smime.p7s
Description: S/MIME cryptographic signature

Re: Releases?

[Wiesner, Martin]

Thx Jon for getting things rolling. Much appreciated!

Best
Martin
-
https://twitter.com/mawiesne

> Am 08.01.2021 um 14:35 schrieb Jean-Louis Monteiro :
> 
> Go for it
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
> 
> 
> On Fri, Jan 8, 2021 at 2:15 PM Jonathan Gallimore <
> jonathan.gallim...@gmail.com> wrote:
> 
>> Hi All,
>> 
>> Any objections if I kick off a 8.0.6 release? I think there are some
>> dependency updates that it would be useful to get included (specifically
>> Tomcat), and also there's a regression with using a non-transactional
>> ActiveMQ connection factory in a transactional method that I have fixed as
>> well.
>> 
>> Thanks
>> 
>> Jon
>> 



smime.p7s
Description: S/MIME cryptographic signature

Re: [VOTE] Release Apache TomEE 8.0.5 and 9.0.0-M3

[Wiesner, Martin]

Hi all,

here’s my 

+1 (non-binding) => for TomEE 8.0.5 

Tested with several projects (primarily web services, JAXB, REST…), 
both on Linux & Mac OS, each under AdoptOpenJDK 11 (latest). 
=> no show stoppers found.

Best
Martin
—
https://twitter.com/mawiesne 


> Am 17.11.2020 um 23:11 schrieb Jonathan Gallimore 
> :
> 
> Hi All,
> 
> This is a first attempt at a vote for a release of Apache TomEE 9.0.0-M3
> and Apache TomEE 8.0.5.
> 
> Maven Repo:
> https://repository.apache.org/content/repositories/orgapachetomee-1177
> https://repository.apache.org/content/repositories/orgapachetomee-1178
> 
> Binaries & Source:
> https://dist.apache.org/repos/dist/dev/tomee/staging-1177/tomee-8.0.5/
> https://dist.apache.org/repos/dist/dev/tomee/staging-1178/tomee-9.0.0-M3/
> 
> Source code:
> TomEE 8.0.5:
> https://dist.apache.org/repos/dist/dev/tomee/staging-1177/tomee-8.0.5/tomee-project-8.0.5-source-release.zip
> TomEE Jakarta Conversion for 9.0.0-M3:
> https://dist.apache.org/repos/dist/dev/tomee/staging-1173/tomee-8.0.4/apache-tomee-9.0.0-M2-source-release.zip
> 
> Tags:
> 
> https://gitbox.apache.org/repos/asf?p=tomee.git;a=tag;h=refs/tags/tomee-8.0.5
> https://gitbox.apache.org/repos/asf?p=tomee-jakarta.git;a=tag;h=refs/tags/tomee-9.0.0-M3
> 
> Release notes:
> 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320=12348622
> 
> (I'll be going through issues and correcting them where they haven't been
> marked as complete)
> 
> Please VOTE:
> 
> [+1] Yes, release it
> [+0] Not fussed
> [-1] Don't release, there's a showstopper (please specify what the
> showstopper is)
> 
> Vote will be open for 72 hours.
> 
> Thanks
> 
> Jon



smime.p7s
Description: S/MIME cryptographic signature

Re: [VOTE] Release TomEE 8.0.4 and 9.0.0-M2

[Wiesner, Martin]

Hi all,

here’s my 

+1 (non-binding)

Tested with several projects (primarily web services, JAXB, REST…), 
both on Linux & Mac OS, each under AdoptOpenJDK 11 (latest). 
=> no show stoppers found.

Best
Martin
—
https://twitter.com/mawiesne 

> Am 23.07.2020 um 17:02 schrieb Jean-Louis Monteiro :
> 
> Hey Jon.
> 
> Did some quick tests and ran TCK. No regression, we even fixed some good
> chunk of tests for better TCK coverage.
> 
> +1
> 
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
> 
> 
> On Thu, Jul 23, 2020 at 3:29 PM Vicente Rossello 
> wrote:
> 
>> Hi,
>> 
>> I've checked the artifacts and played a bit with the plus server.
>> 
>> +1
>> 
>> On Thu, Jul 23, 2020 at 2:58 PM Zowalla, Richard <
>> richard.zowa...@hs-heilbronn.de> wrote:
>> 
>>> Thanks for the exaplantion, Jon. I will take a look at the transformer
>>> and apply it to our application after I have returned from vacation.
>>> 
>>> For now:
>>> 
>>> Take my +1 (although I've only tested 8.0.4 as stated in my original
>>> mail).
>>> 
>>> Am Donnerstag, den 23.07.2020, 12:41 +0100 schrieb Jonathan Gallimore:
>>> 
>>> Hi Richard
>>> 
>>> 
>>> The artifacts are here:
>>> 
>>> https://repository.apache.org/content/repositories/orgapachetomee-1173/org/apache/tomee/jakarta/apache-tomee/9.0.0-M2/
>>> 
>>> 
>>> (note the org.apache.tomee.jakarta group ID).
>>> 
>>> 
>>> The transformation tool currently only works on zips, which is why we don't
>>> 
>>> (yet) have tar.gzs there.
>>> 
>>> 
>>> Its worth taking a look at the Eclipse Transformer to transform your
>>> 
>>> applications. This is another case where I'd expect issues, and encourage
>>> 
>>> you to report them. I'm also a committer on that project and would be keen
>>> 
>>> to help with any improvements. Here's how we do it on Moviefun:
>>> 
>>> https://github.com/apache/tomee/blob/master/examples/moviefun/pom.xml#L111-L126
>>> 
>>> .
>>> 
>>> 
>>> We're not able to translate javax -> jakarta "on the fly". I have looked at
>>> 
>>> this, and theoretically its possible to create a java agent to do this, but
>>> 
>>> it comes unstuck where various libraries inspect classes for annotations,
>>> 
>>> and none of them actually *load* the class to do that (so it doesn't get
>>> 
>>> translated, and subsequently fails). Unfortunately, the renaming means
>>> 
>>> we'll all need to make changes to our applications at some point.
>>> 
>>> 
>>> Jon
>>> 
>>> 
>>> On Thu, Jul 23, 2020 at 12:04 PM Zowalla, Richard <
>>> 
>>> richard.zowa...@hs-heilbronn.de> wrote:
>>> 
>>> 
>>> Hi Jon,
>>> 
>>> 
>>> thanks for the explanation.
>>> 
>>> 
>>> The artifacts for 9.0.0-M2 seem to be missing in the Maven staging
>>> 
>>> repository? Is this known/planned in this way?
>>> 
>>> 
>>> I just wanted to build our project (which works fine with 8.0.4) with
>>> 
>>> the 9.0.0-M2 artifacts.
>>> 
>>> 
>>> Thanks,
>>> 
>>> Richard
>>> 
>>> 
>>> 
>>> Am Donnerstag, den 23.07.2020, 10:39 +0100 schrieb Jonathan Gallimore:
>>> 
>>> Dammit, accidentally hit send far too soon. Here's the whole message:
>>> 
>>> 
>>> 
>>> Hi folks
>>> 
>>> 
>>> Thanks for the reviews and feedback so far.
>>> 
>>> 
>>> I've seen a couple of comments come in that I just wanted to
>>> 
>>> briefly address.
>>> 
>>> 
>>> The vote is TomEE 8.0.4 *and* 9.0.0-M2. A +1 is a +1 for both. You
>>> 
>>> can't
>>> 
>>> vote +1 for 8.0.4 and 0 (or abstain) for 9.0.0-M2, for example. I can
>>> 
>>> cancel this vote, re-roll, and issue a separate vote for the 2, if we
>>> 
>>> wish.
>>> 
>>> I didn't do this on this occasion, because we're producing the binary
>>> 
>>> that
>>> 
>>> uses javax (8.0.4) and then transforming it to produce the version
>>> 
>>> that
>>> 
>>> uses jakarta (9.0.0-M2), but can do so going forward.
>>> 
>>> 
>>> We don't expect 9.0.0-M2 to be perfect. We're grateful if you can
>>> 
>>> report
>>> 
>>> issues you find, but that shouldn't necessarily block the release. I
>>> 
>>> totally understand that migrating your own projects to the jakarta
>>> 
>>> namespace is a big deal and unlikely to be feasible for a vote. If
>>> 
>>> you can
>>> 
>>> check you can download it and boot it up, and check for any legal
>>> 
>>> issues,
>>> 
>>> bad libraries etc, that helps. If you'd like an example app to try,
>>> 
>>> do try
>>> 
>>> building the moviefun example. That (like many of the examples)
>>> 
>>> produces
>>> 
>>> both javax and jakarta .war files.
>>> 
>>> 
>>> Jean-Louis is going to run the TCK against this, which is fantastic.
>>> 
>>> A
>>> 
>>> couple of notes here to set expectations - I'm not expecting a full
>>> 
>>> pass,
>>> 
>>> but I'm also not expecting regressions, so passing the TCK shouldn't
>>> 
>>> block
>>> 
>>> the release. I did have to comment out the new security module (sorry
>>> 
>>> -
>>> 
>>> there were some JAX-RS test failures with it), so those tests still
>>> 
>>> won't
>>> 
>>> pass.
>>> 
>>> 
>>> Hope that all makes sense, but 

Re: [VOTE] Release TomEE 8.0.2

[Wiesner, Martin]

Hi all,

+1 (non-binding)

Tested with several projects (primarily web services, JAXB, REST…), 
both on Linux & Mac OS, each under AdoptOpenJDK 11 (latest).

Thanks @Jon and all others who contributed to this (upcoming) release.

Best
Martin
—
https://twitter.com/mawiesne 


> Am 13.05.2020 um 16:39 schrieb Jonathan Gallimore 
> :
> 
> Hi All,
> 
> Here's a second attempt at releasing of TomEE 8.0.2. Please can you take a
> careful look, review, test and provide feedback.
> 
> Maven Repo:
> https://repository.apache.org/content/repositories/orgapachetomee-1167
> 
> Binaries & Source:
> https://dist.apache.org/repos/dist/dev/tomee/staging-1167/tomee-8.0.2
> 
> Tag:
> 
> https://gitbox.apache.org/repos/asf?p=tomee.git;a=tag;h=refs/tags/tomee-8.0.2
> 
> Release notes:
> 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320=12346650
> 
> Please VOTE:
> 
> [+1] Yes, release it
> [+0] Not fussed
> [-1] Don't release, there's a showstopper (please specify what the
> showstopper is)
> 
> Vote will be open for 72 hours or as needed.
> 
> Thanks
> 
> Jon




smime.p7s
Description: S/MIME cryptographic signature

Re: [VOTE] Release TomEE 8.0.1

[Wiesner, Martin]

+1 (non-binding)

Tested with several WAR projects (primarily web services, JAXB, REST…)

Best
Martin
—
https://twitter.com/mawiesne 


> Am 08.01.2020 um 22:32 schrieb Cesar Hernandez :
> 
> +1
> 
> El mié., 8 ene. 2020 a las 14:14, Daniel Dias Dos Santos (<
> daniel.dias.analist...@gmail.com>) escribió:
> 
>> +1 :  )
>> --
>> 
>> *Daniel Dias dos Santos*
>> Java Developer
>> SouJava & JCP Member
>> GitHub: https://github.com/Daniel-Dos
>> Linkedin: www.linkedin.com/in/danieldiasjava
>> Twitter: http://twitter.com/danieldiasjava
>> 
>> 
>> Em qua., 8 de jan. de 2020 às 11:52, Daniel Cunha 
>> escreveu:
>> 
>>> +1
>>> 
>>> Em qua., 8 de jan. de 2020 às 11:44, Marco Ferreira <
>>> marcoantoniobferre...@gmail.com> escreveu:
>>> 
 +1
 
 On Wed, 8 Jan 2020 at 07:18, Jonathan Gallimore <
 jonathan.gallim...@gmail.com> wrote:
 
> Hi All,
> 
> Here's a second attempt at roll of a TomEE 8.0.1. Please can you
>> take a
> careful look, review, test and provide feedback.
> 
> Maven Repo:
> 
>>> https://repository.apache.org/content/repositories/orgapachetomee-1161/
> 
> Binaries & Source:
> 
>> https://dist.apache.org/repos/dist/dev/tomee/staging-1161/tomee-8.0.1/
> 
> Tag:
> 
> 
> 
 
>>> 
>> https://gitbox.apache.org/repos/asf?p=tomee.git;a=tag;h=refs/tags/tomee-8.0.1
> 
> Release notes:
> 
> 
> 
 
>>> 
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320=12346179
> 
> The previous votes were cancelled after an issue was found with TomEE
 7.1.2
> (https://issues.apache.org/jira/browse/TOMEE-2758) and the release
>> for
> 7.0.7 had incorrect artifacts. The binary here should be the same as
>>> the
> previous vote, so if you were ok with that, theoretically this one
>>> should
> be ok too - but please check.
> 
> Please VOTE:
> 
> [+1] Yes, release it
> [+0] Not fussed
> [-1] Don't release, there's a showstopper (please specify what the
> showstopper is)
> 
> Vote will be open for 72 hours or as needed.
> 
> Thanks
> 
> Jon
> 
 
 
 --
 AAte
 
 Atenciosamente,
 
 Marco Ferreira
 [image: https://]about.me/m.ferreira
 <
 
>>> 
>> https://about.me/m.ferreira?promo=email_sig_source=product_medium=email_sig_campaign=gmail_api
> 
 
>>> 
>>> 
>>> --
>>> Daniel "soro" Cunha
>>> https://twitter.com/dvlc_
>>> 
>> 
> 
> 
> -- 
> Atentamente:
> César Hernández.



smime.p7s
Description: S/MIME cryptographic signature

Re: [VOTE] Release TomEE 8.0.1

[Wiesner, Martin]

+1

Best
Martin

> Am 23.12.2019 um 16:50 schrieb Cesar Hernandez :
> 
> +1
> 
> On Mon, Dec 23, 2019 at 07:20 Richard Monson-Haefel 
> wrote:
> 
>> +1
>> 
>> On Mon, Dec 23, 2019 at 1:12 AM Jean-Louis Monteiro <
>> jlmonte...@tomitribe.com> wrote:
>> 
>>> +1
>>> 
>>> Le dim. 22 déc. 2019 à 10:13, Mark Struberg 
>> a
>>> écrit :
>>> 
 +1
 
 LieGrue,
 strub
 
 
> Am 19.12.2019 um 08:19 schrieb Jonathan Gallimore <
 jonathan.gallim...@gmail.com>:
> 
> Hi All,
> 
> Here's a first attempt at roll of a TomEE 8.0.1. Please can you take
>> a
> careful look, review, test and provide feedback.
> 
> Maven Repo:
> 
>>> https://repository.apache.org/content/repositories/orgapachetomee-1156/
> 
> Binaries & Source:
> 
>> https://dist.apache.org/repos/dist/dev/tomee/staging-1156/tomee-8.0.1/
> 
> Tag:
> 
> 
 
>>> 
>> https://gitbox.apache.org/repos/asf?p=tomee.git;a=tag;h=refs/tags/tomee-8.0.1
> 
> Release notes:
> 
> 
 
>>> 
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320=12346179
> 
> Please VOTE:
> 
> [+1] Yes, release it
> [+0] Not fussed
> [-1] Don't release, there's a showstopper (please specify what the
> showstopper is)
> 
> Vote will be open for 72 hours or as needed.
> 
> Thanks
> 
> Jon
 
 
>>> 
>> 
>> 
>> --
>> Richard Monson-Haefel
>> https://twitter.com/rmonson
>> https://www.linkedin.com/in/monsonhaefel/
>> 
> -- 
> Atentamente:
> César Hernández.
—
https://twitter.com/mawiesne

Re: [VOTE] TomEE 8.0.0-M3 (staging-1136) - take two

[Wiesner, Martin]

Hi guys,

+1 (non binding)

Big thanks for this release.

Best
Martin
--
https://twitter.com/mawiesne

Re: Jakarta EE namespace discussion

[Wiesner, Martin]

Dear Mark, dear David,

thanks for all the energy and „drive" you are offering in the current 
situation. Many ppl in the community appreciate your work and all related 
contributions A LOT.

Let’s emphasize the opportunities over all those barriers.

Best
Martin
—
https://twitter.com/mawiesne


Am 07.05.2019 um 20:16 schrieb Mark Struberg 
mailto:strub...@yahoo.de.INVALID>>:

And here is some more in-depth technical information
https://struberg.wordpress.com/2019/05/06/the-way-forward-for-jakartaee-packages/

Already trying out how well Option C (big-bang, Davids 1) would work and what 
borders we'd hit.

Copying over what I wrote on the tomcat list:
---
I've also already started to migrate a few spec packages.
The current work in progress is available here:
https://svn.apache.org/repos/asf/geronimo/specs/branches/jakarta/

I've already test-migrated over Apache OpenWebBeans CDI container.
Of course with TCK and servlet integration disabled for now as Arquillian and 
Tomcat first needs to be ported.
https://github.com/struberg/openwebbeans/tree/jakarta

I'm right now tinkering with Tomcat.
And boy, tomcat has way more dependencies than I'd like.
And it would help if it would finally be migrated to use Maven, but I spare you 
that ;)

As soon as I've something decently working then I'll share!



LieGrue,
strub

Re: Another 8.0.0 milestone release

[Wiesner, Martin]

Hi all,

+1 


Pls, also keep the release of 7.1.x (x=1) in mind, as the Java 11 
out-of-the-box experience is crucial for many users in the community.

Best Martin
—
https://twitter.com/mawiesne 



smime.p7s
Description: S/MIME cryptographic signature

Re: Performance issue with JMS on Tomee 7.0.5

[Wiesner, Martin]

Thanks Jonathan for such a quick reaction and the openness to provide a MWE for 
that issue to the community.

Best
Martin
—
https://twitter.com/mawiesne 




smime.p7s
Description: S/MIME cryptographic signature

Re: Performance issue with JMS on Tomee 7.0.5

[Wiesner, Martin]

Hi Jonathan,

could you open a JIRA for the below topic, please? It makes it a lot easier to 
track the weird behaviour and it is so important to document your observations. 
Thereby, we’ll be able to reference this issue in upcoming discussions. Please 
put additional material into the JIRA, as long as you can provide it (legally 
speaking).

Optional: Can you a MWE that demonstrates the issue somehow?

Best
Martin
—
https://twitter.com/mawiesne 


> Am 07.01.2019 um 03:47 schrieb exabrial12 :
> 
> Hey guys,
> 
> We're noticing a pretty strange issue processing a large number of JMS
> messages. After about 20k messages, messages consumed per second drops off
> and there's heavy GC activity (smells like a memory leak). What interesting
> though is the server continues to run and doesn't OutOfMemoryError. A simple
> restart of TomEE (but not the broker) temporarily fixes the problem. We're
> using an external broker, not the internal one
> 
> What's interesting, is that Jonathan Gallimore and I were talking about a
> similar issue with Websockets. We noticed that eventually the servers will
> exhibit the same behavior once enough websockets are opened and closed. This
> issue occurs infrequently enough because we might handle 20,000 websockets
> over the course of a few days, but we can process 20,000 JMS messages in a
> few mins.
> 
> 
> I have a heap dump from the issue and several jstacks. I'll be honest, I'm
> not sure where to start. In the past I've solved memory leaks by careful
> code audits. Our codebase happens to be mostly stateless, with everything
> else being managed by CDI scopes (ApplicationScoped and TransactionScoped).
> 
> What's a good way to get started?
> 
> 
> 
> --
> Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html



smime.p7s
Description: S/MIME cryptographic signature

Is TomEE ready to ship for Santa? - Conducting pre-xmas releases: 7.0.6, 7.1.1, 8.0.0-M2

[Wiesner, Martin]

Hey guys,

Richard (Z, @rzo1) and me are having some coffee in the office and are 
discussing several ideas. One them is that we’d like to propose that TomEE 
project kicks out a pre-xmas release for 7.1.1 and/or 7.0.6, and even more 
interesting: a 8.0.0-M2 milestone preview. 

The rationale behind it is that we all might get (more) valuable feedback on 
the current state by the TomEE community. With many bugs fixed and improvements 
made recently, it might be worth considering such a step.

What do you all think of our proposal? Any opinions much welcome.

Best
Martin
--
https://twitter.com/mawiesne 



smime.p7s
Description: S/MIME cryptographic signature

Re: TOMEE-2234 BMP finder issue

[Wiesner, Martin]

Hi Jon,

TOMEE-2234 has originally been reported as a bug for 1.7.3 and 7.0.5. Thus, I 
think it should be fixed at least at on both 7.x branches. Could you merge a 
backport of these changes to 1.7.x, 7.0.x and/or 7.1.x maintenance branches? If 
conducted it will compatible with the original report and we’ll fix it 
consistently with the 8.0.x master branch. 

In this context, I'll wait with resolving this issue in JIRA for some 
days/weeks.

Best
Martin
—
https://twitter.com/mawiesne 


> Am 12.12.2018 um 11:46 schrieb Jonathan Gallimore 
> :
> 
> Still testing, but here's the change:
> https://github.com/apache/tomee/pull/272. Any feedback is welcome.
> 
> Jon
> 
> On Wed, Dec 12, 2018 at 10:29 AM Jonathan Gallimore <
> jonathan.gallim...@gmail.com> wrote:
> 
>> I found the issue here, and fixed it. I need to check to ensure that the
>> change doesn't affect the wire protocol - I'm _fairly_ sure it doesn't, but
>> we'd need to discuss how to handle it, if it did. I should have a PR up for
>> review later today.
>> 
>> Jon
>> 
>> 
>> 
>> On Tue, Dec 11, 2018 at 2:34 PM Jonathan Gallimore <
>> jonathan.gallim...@gmail.com> wrote:
>> 
>>> I added a comment to the JIRA, but I'll follow up here too. I started
>>> writing a test for this, and made a couple of small changes:
>>> 
>>> * flipped your beans from remote to local
>>> * added a servlet rather than a main
>>> * introduced  in ejb-jar.xml and web.xml so they can be
>>> looked up via java:comp/env as opposed to the global JNDI name
>>> put everything in a .war as opposed to .ear
>>> 
>>> ... and it works.
>>> 
>>> Generated .war file and source attached. I'm not entirely sure which of
>>> my changes has enabled it to work - my current guess is its the remote ->
>>> local change, but I'll dig into each one.
>>> 
>>> Interesting problem - thanks for reporting it!
>>> 
>>> Jon
>>> 
>>> On Mon, Dec 10, 2018 at 7:43 PM Jonathan Gallimore <
>>> jonathan.gallim...@gmail.com> wrote:
>>> 
 Hi all
 
 I noticed this come in on JIRA:
 https://issues.apache.org/jira/browse/TOMEE-2234
 
 Seems we have an issue returning more than 256 entities from a BMP
 finder. Given that I've worked in and around this area, I'd like to work on
 it. I'll assign it to me, but if you had a burning desire to tackle it, let
 me know.
 
 Thanks
 
 Jon
 
>>> 



smime.p7s
Description: S/MIME cryptographic signature

Re: More Community Website section improvements [TOMEE-2317]

[Wiesner, Martin]

Hi César,

I just marked this issue as resolved per PR 11. Thanks for your input and work 
on this.

Best
Martin
—
https://twitter.com/mawiesne 

> Am 13.12.2018 um 07:22 schrieb César Hernández Mendoza :
> 
> Hi,
> The PR is now part of master, but the JIRA ticket is still in Open state
> and unassigned.
> It's ok to ask to the list for JIRA admins to move forward the ticket or
> before each release, the Jira admins do the JIRA pruning?
> 
> 
> El mar., 4 dic. 2018 a las 13:08, César Hernández Mendoza (<
> cesargu...@gmail.com>) escribió:
> 
>> Hi,
>> 
>> I created https://issues.apache.org/jira/browse/TOMEE-2317 and its PR
>> include the migration of the Contribution Tips from the old site. I added
>> in the Ticket a short video of the PR.
>> 
>> Can some of the admins please assign the ticket to me for further tracking.
>> 
>> @Richard Monson,
>> I literally copy and paste the snippet of text you have been sharing via
>> email for people knowing how to subscribe to the mailing list. Feel free to
>> keep improving this content.
>> 
>> @Frank Jung
>> I added you feedback from TOMEE-2300 into this new Ticket and PR. Thank
>> you.
>> 
>> --
>> Atentamente:
>> César Hernández Mendoza.
>> 
> 
> 
> -- 
> Atentamente:
> César Hernández Mendoza.




smime.p7s
Description: S/MIME cryptographic signature

Re: Update the API code

[Wiesner, Martin]

Hi all,

I fully agree with Jon’s thoughts: Lamda expressions are no silver bullet, as 
mentioned by him... Using 'foreach' more often, is valid as readability is 
increased and somehow this feels "natural“ nowadays.

Best
Martin
—
https://twitter.com/mawiesne

> Am 05.12.2018 um 17:21 schrieb Jonathan Gallimore 
> :
> 
> Just my two cents...
> 
> I don't any issue with switching to foreach, like shown in the example
> given. I personally would not want to switch to lambdas everywhere "just
> because we can". I've seen some really awful code using lambdas everywhere
> just because it could. Turned out to be much harder to read rather than
> easier. The other issue is if we make sweeping changes right across the
> codebase, we risk getting conflicts with on-going work in people's PRs.
> 
> Code cleanup and making it easier to read is welcome, but I'd suggest
> breaking it up into small specific pieces rather than broad PRs, and
> discussing the changes here.
> 
> Thanks
> 
> Jon
> 
> On Wed, Dec 5, 2018 at 3:39 PM Bruno Baptista  wrote:
> 
>> Actually... What Richard said changed my mind.
>> 
>> Why not just use a foreach lambda when possible?
>> 
>> Bruno Baptista
>> https://twitter.com/brunobat_
>> 
>> 
>> On 05/12/18 15:34, Richard Zowalla wrote:
>>> Hey,
>>> 
>>> imho it would be a good improvement to reduce legacy code constructs
>> from below Java 8 in the master branch.
>>> 
>>> Some PRs are just merged into the master related to the use of diamond
>> operator etc. and other stuff.
>>> 
>>> However, we should come to some general agreement about this imho.
>>> 
>>> And of course open a JIRA to signalize someone is working on it.
>>> 
>>> Just my personal opinion.
>>> 
>>> Best,
>>> Richard
>>> 
>>> 
>>> Am 5. Dezember 2018 16:27:50 MEZ schrieb "Otávio Gonçalves de Santana" <
>> osant...@tomitribe.com>:
 Hello everyone, I'm studying the code, mostly the container module. It
 seems that in the master we support Java 8.
 My question: Does make sense to create PRs to update some APIs to a
 modern
 way?
 I mean, e.g.:
 
 for (int i = 0; i < rules.length; i++) {
rules[i].validate(appModule);
 }
 
 To
 
 for (ValidationRule rule : rules) {
rule.validate(appModule);
 }
 
 
 
 Ps: That does not impact in performance, just does the code
 cleaner/readable and more natural to maintainer IMHO.
>> 




smime.p7s
Description: S/MIME cryptographic signature

Re: Hello World! - How can I help?

[Wiesner, Martin]

Hi Jon,

my JIRA ID simply is: "mawiesne"

Best,
mawiesne
--
https://twitter.com/mawiesne <https://twitter.com/mawiesne>

> Am 01.12.2018 um 00:52 schrieb Jonathan Gallimore 
> :
> 
> Hi Martin
> 
> Can you let me know your JIRA ID and I'll put you in the contributors group.
> 
> Many thanks
> 
> Jon
> 
> On Fri, Nov 30, 2018 at 11:24 PM Jonathan Gallimore <
> jonathan.gallim...@gmail.com> wrote:
> 
>> Hi Martin!
>> 
>> Thanks for posting, and welcome! I think it would be great to have your
>> support on the JIRA side of things - many thanks for offering. I think our
>> JIRA titles and descriptions in many cases probably only make sense to the
>> developer who filed the ticket and probably doesn't mean too much to folks
>> consuming the software. Any help you could give would be fantastic.
>> 
>> I don't know what is involved permissions wise, but @David - perhaps you
>> could help? We also have some folks I can assign issues to, and some I
>> cannot. I don't have karma to make group changes. Happy to help if I can
>> but I might need some more permissions myself :).
>> 
>> Cheers
>> 
>> Jon
>> 
>> On Fri, Nov 30, 2018 at 10:41 PM Wiesner, Martin <
>> martin.wies...@hs-heilbronn.de> wrote:
>> 
>>> Hi folks,
>>> 
>>> my name is Martin. @dblevins and I were discussing how individuals could
>>> contribute to #TomEE. He convinced me to join the mailing list.
>>> In the past, I contributed some user feedback, opened bug reports and
>>> proposed improvements in exchange with @rmannibucau and @struberg.
>>> 
>>> Some further background information:
>>> I work in the field of Medical Informatics, doing research and teaching
>>> for several years now at Heilbronn University (Germany), CS faculty. As
>>> Richard (@zowalla) already mentioned in his welcome message, we are using
>>> TomEE in software labs in our bachelor / master programmes and in regular
>>> projects at our faculty, for instance, managing hardware loans to students
>>> and staff members.
>>> 
>>> How I could contribute (atm):
>>> @dblevins and I discussed that I can support in keeping TomEE's JIRA
>>> instance clean and comprehensible, e.g. by (a) identifying and closing
>>> duplicates, (b) clarifying unclear descriptions or affected branches, (c)
>>> communicating with reporters on missing details and so on and so forth.
>>> Hopefully, other dev guys could benefit. Why? They might better identify
>>> relevant topics or enhance existing bug reports... In addition, I could
>>> screen discussions on the mailing list for "hidden gems" and open (or edit)
>>> JIRA issues to give bugs and/or tasks a unique number within the issue
>>> tracker.
>>> 
>>> Why is this so important?
>>> From my perspective, as a researcher and as software architect, clarity
>>> often improves communication in, and efficiency of a project. I've
>>> experienced this in many projects I’ve been involved so far.
>>> 
>>> What do I suggest?
>>> Maybe you can grant me elevated permissions within the project’s issue
>>> tracker. If approved, I could then manage the aforementioned aspects within
>>> TomEE’s JIRA instance. I’m familiar with this tooling as we have JIRA
>>> running in our faculty. This instance is actually hosted by Richard and me.
>>> 
>>> If I can help otherwise: feel free to ask. In case I say ’no’: please
>>> don’t feel rejected. I’ll try to give an explanation in such a case.
>>> 
>>> Best,
>>> mawiesne
>>> --
>>> https://twitter.com/mawiesne
>>> 
>> 

--
Dipl.-Inform. Med. Martin Wiesner
Research Associate





Hochschule Heilbronn – University of Applied Sciences
Max-Planck-Str. 39 
D-74081 Heilbronn 

phone: +49 (0)7131 - 504 1124 bzw. 504 6947 
fax: +49 (0)7131 - 252 470 
mail: martin.wies...@hs-heilbronn.de <mailto:martin.wies...@hs-heilbronn.de> 
web: http://www.mi.hs-heilbronn.de/ <http://www.mi.hs-heilbronn.de/>

GMDS-AG Consumer Health Informatics
web: 
https://gmds.de/aktivitaeten/medizinische-informatik/arbeitsgruppenseiten/consumer-health-informatics-chi
 
<https://gmds.de/aktivitaeten/medizinische-informatik/arbeitsgruppenseiten/consumer-health-informatics-chi/>





smime.p7s
Description: S/MIME cryptographic signature

Re: How can I help?

[Wiesner, Martin]

Hi César and Hayri,

I very much support César's suggestion to open a JIRA issue per PR (or even 
upfront so others can comment or point you to existing resources early). 
Thereby, other devs might better check which branches or what parts of TomEE 
are affected, or what the intention of an improvement is.

Best,
mawiesne
--
https://twitter.com/mawiesne 

> Am 30.11.2018 um 23:17 schrieb César Hernández Mendoza :
> 
> btw, Hayri, I recommend you to create a Jira for your Pr's. [1]
> Base on my experience, it's better to have this tracking so you can then
> see the status of your PR (in a review, assigned, etc).
> 
> 
> [1] https://issues.apache.org/jira/projects/TOMEE/summary
> 
> El vie., 30 nov. 2018 a las 16:13, Hayri Cicek ()
> escribió:
> 
>> Thanks César
>> 
>> Den fre 30 nov. 2018 20:40 skrev César Hernández Mendoza <
>> cesargu...@gmail.com>:
>> 
>>> Hi Hayri,
>>> 
>>> Welcome back, since the current master is Java 8 compliant [1], I think
>>> both PR's are good improvements to code clean up.
>>> 
>>> 
>>> [1] https://github.com/apache/tomee/blob/master/pom.xml#L98-L99
>>> 
>>> El vie., 30 nov. 2018 a las 13:12, Hayri Cicek ()
>>> escribió:
>>> 
 Hi everyone,
 
 My name is Hayri Cicek and we use TomEE everyday where I work and would
 love to contribute back to the project and
 I saw the how can I help and would love to try help but I started
>> trying
>>> to
 contribute about 3 month ago and have 2 PR's where I did some final
 parameters and use of diamond operator and would love to see if the
>> PR's
 are okej or if not then I would love to help with something else 
 
 Links to PR's
 https://github.com/apache/tomee/pull/168
 
 https://github.com/apache/tomee/pull/163
 
 Best regards
 Hayri Cicek
 https://kodnito.com
 
>>> 
>>> 
>>> --
>>> Atentamente:
>>> César Hernández Mendoza.
>>> 
>> 
> 
> 
> -- 
> Atentamente:
> César Hernández Mendoza.



smime.p7s
Description: S/MIME cryptographic signature

Hello World! - How can I help?

[Wiesner, Martin]

Hi folks,

my name is Martin. @dblevins and I were discussing how individuals could 
contribute to #TomEE. He convinced me to join the mailing list.
In the past, I contributed some user feedback, opened bug reports and proposed 
improvements in exchange with @rmannibucau and @struberg.

Some further background information: 
I work in the field of Medical Informatics, doing research and teaching for 
several years now at Heilbronn University (Germany), CS faculty. As Richard 
(@zowalla) already mentioned in his welcome message, we are using TomEE in 
software labs in our bachelor / master programmes and in regular projects at 
our faculty, for instance, managing hardware loans to students and staff 
members.

How I could contribute (atm):
@dblevins and I discussed that I can support in keeping TomEE's JIRA instance 
clean and comprehensible, e.g. by (a) identifying and closing duplicates, (b) 
clarifying unclear descriptions or affected branches, (c) communicating with 
reporters on missing details and so on and so forth. Hopefully, other dev guys 
could benefit. Why? They might better identify relevant topics or enhance 
existing bug reports... In addition, I could screen discussions on the mailing 
list for "hidden gems" and open (or edit) JIRA issues to give bugs and/or tasks 
a unique number within the issue tracker. 

Why is this so important? 
From my perspective, as a researcher and as software architect, clarity often 
improves communication in, and efficiency of a project. I've experienced this 
in many projects I’ve been involved so far.

What do I suggest?
Maybe you can grant me elevated permissions within the project’s issue tracker. 
If approved, I could then manage the aforementioned aspects within TomEE’s JIRA 
instance. I’m familiar with this tooling as we have JIRA running in our 
faculty. This instance is actually hosted by Richard and me.

If I can help otherwise: feel free to ask. In case I say ’no’: please don’t 
feel rejected. I’ll try to give an explanation in such a case.

Best,
mawiesne
--
https://twitter.com/mawiesne

smime.p7s
Description: S/MIME cryptographic signature