Deploying WAR in TomEE

I have my WAR inside webapps of TomEE. After delpoying, when I try to run the application, it says it is not able to see the classes that are present under Project/WEB-INF/classes. I created the WAR file from eclipse by right clicking the project and selecting Export as WAR file. I also tried

RE: [Newsletter] Re: [Newsletter] Re: Migration step of jtaManaged flag in context resources

http://tomee.apache.org/datasource-config.html 'Alternatively, a DataSource can be declared via properties in the /conf/system.properties file or via Java VirtualMachine -D properties. ' This is what I'm planning to use (Java VirtualMachine -D properties) in a K8 cluster, should satisfy the

Re: TomEE Stable and OpenJDK

Exact dates are hard to provide. As a rough idea, we'll need a OpenJPA release, and I think Mark is kicking that off soon, and then I think we're probably good to go. The TomEE release can take a week or to, depending on any issues that crop up, and allowing enough time to vote. Hope that is some

RE: TomEE Stable and OpenJDK

Hello Romain and Mark, If I have understood you well, TomEE 8 will address µProfile 1.3 since its first version. But what about my first question regarding 7.0.5 ? Best Regards. -Original Message- From: Romain Manni-Bucau [mailto:rmannibu...@gmail.com] Sent: lundi 14 mai 2018 15:17

Re: TomEE Stable and OpenJDK

Le lun. 14 mai 2018 13:16, COURTAULT Francois < francois.courta...@gemalto.com> a écrit : > Hello Mark, > > Thanks a lot for sharing the TomEE roadmap. > > My main concerns about TomEE are: > - java 9 and above support (java 10 and 11) > - JavaEE 8 specification support > - µProfile

Re: [Newsletter] Migration step of jtaManaged flag in context resources

Yup. In my book the conf/tomee.xml is the most portable one. Becaue here you clearly defer all infrastructure configuration to the container. Of course for WildFly, Payara, etc the way how to configure the infrastructure is different. But the WAR will be perfectly portable in this case.

RE: TomEE Stable and OpenJDK

Hello Mark, Thanks a lot for sharing the TomEE roadmap. My main concerns about TomEE are: - java 9 and above support (java 10 and 11) - JavaEE 8 specification support - µProfile follow up: no TomEE µProfile released yet whereas others exist today like Payara micro, Wildfly Swarm

Re: [Newsletter] Re: [Newsletter] Re: Migration step of jtaManaged flag in context resources

Le lun. 14 mai 2018 09:56, a écrit : > So bottom line: There is no portable DataSource definition technique as > they are part of the container and hence container specific? > Yes, portable solution is an app datasource which breaks the injection pattern :(

RE: [Newsletter] Re: [Newsletter] Re: Migration step of jtaManaged flag in context resources

So bottom line: There is no portable DataSource definition technique as they are part of the container and hence container specific? -Original Message- From: Romain Manni-Bucau Sent: Monday, May 14, 2018 10:52 AM To: users@tomee.apache.org Subject: *EXT*

Re: [Newsletter] Re: Migration step of jtaManaged flag in context resources

Not portable but same as context.xml ;) @DataSourceDefinition is not too :( - properties are not Le lun. 14 mai 2018 07:57, a écrit : > Hi Mark and Romain, > > thanks for your replies! > > Is the resources.xml approach a portable solution? E.g. if we want to

RE: [Newsletter] Re: Migration step of jtaManaged flag in context resources

Hi Mark and Romain, thanks for your replies! Is the resources.xml approach a portable solution? E.g. if we want to support Wildfly in the future, which approach is the most portable? Tomee.conf doesn’t sound too portable :) Thanks and best Fabian -Original Message- From: Mark