Re: Custom DynamicDeployer

Thanks Romain, I cannot make it work without explicitly defining a Resource somewhere, now I will give a try to the observers. On Thu, Jul 14, 2016 at 2:45 PM, Romain Manni-Bucau <rmannibu...@gmail.com> wrote: > Le 14 juil. 2016 13:11, "Lazar Kirchev" <lazar.kirc

Re: Custom DynamicDeployer

, Romain Manni-Bucau <rmannibu...@gmail.com> wrote: > 2016-07-13 16:36 GMT+02:00 Lazar Kirchev <lazar.kirc...@gmail.com>: > > > I need to create resources on the fly based on ResourceRefs, without any > > resource definition in resources.xml or context.xml. I cou

Re: Getting ConfigurationException: Factory ClientWindowFactory was not configured properly

Hi, I got exactly the same problem when deploying an app without beans.xml. However, I tried to deploy it on Tomcat + OpenWebBeans + Mojarra and it worked fine. What do you think? Regards, Lazar On Fri, Aug 5, 2016 at 7:25 PM, Romain Manni-Bucau wrote: > feel free to

Re: Getting ConfigurationException: Factory ClientWindowFactory was not configured properly

Blog > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog > <http://rmannibucau.wordpress.com> | Github <https://github.com/ > rmannibucau> | > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber > <http://www.tomitribe.com> | JavaEE Facto

Re: Getting ConfigurationException: Factory ClientWindowFactory was not configured properly

d Wordpress Blog > <http://rmannibucau.wordpress.com> | Github <https://github.com/ > rmannibucau> | > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber > <http://www.tomitribe.com> | JavaEE Factory > <https://javaeefactory-rmannibucau

TomEE 7.0.1 does not recognize deny-uncovered-http-methods web.xml element

Hello, I noticed that TomEE 7.0.1 does not recognize the servlet 3.1 web.xml element deny-uncovered-http-methods. Deploying an application with this element in the descriptor results in the following exception: org.apache.openejb.OpenEJBException: Cannot unmarshall the web.xml file:

Custom DynamicDeployer

Hello, The OpenEJB's ConfigurationFactory supports providing a custom DynamicDeployer to it. Does Tomee provide any means to configure such a custom DynamicDeployer, or is this completely hidden? Regards, Lazar

Re: Custom DynamicDeployer

lt; > https://github.com/rmannibucau> | > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber > <http://www.tomitribe.com> | JavaEE Factory > <https://javaeefactory-rmannibucau.rhcloud.com> > > 2016-07-13 16:02 GMT+02:00 Lazar Kirchev <lazar.kirc

Re: Separating the SystemInstance initialization from the TomcatLoader initialization

Hello Romain, It seems the commit https://github.com/apache/tomee/commit/ed37f9ee3995812ae91a19cf36a85d534787cefa does not fix the issue in TOMEE-1875. It is in the TomcatWebAppBuilder's constructor and it tries to get the ConfigurationFactory if already created, but this gets executed before the

Question about web services support

Hello, I noticed that in TomcatWsRegistry's constructor the first service with engine container is used to initialize the registry. And after that in the setWsContainer this engine is used to search for the contextRoot of the application being deployed. However, it is a valid scenario to have

Java EE API versions

Hello, I noticed several differences between the versions of the specifications in Java EE 7 and the versions described in the javaee-api-feature.xml file in javaee-api-7.0.jar file. For example: JTA 1.2 -> mvn:org.apache.geronimo.specs/geronimo-jta_1.1_spec/${geronimo-jta_1.1_spec.version}

Re: Java EE API versions

/blog-rmannibucau.rhcloud.com> | Old Wordpress Blog > <http://rmannibucau.wordpress.com> | Github <https://github.com/ > rmannibucau> | > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber > <http://www.tomitribe.com> | JavaEE Factory > <https:/

Tomee plume maven coordinate

Hello, What are the maven coordinates of Tomee plume zip? Is there such thing as org.apache.tomee apache-tomee 7.0.3 zip plume Or they are different? Regards, Lazar

Re: Dependencies of jstl implementation 1.2.5

blog-rmannibucau.rhcloud.com> | Old Blog > <http://rmannibucau.wordpress.com> | Github <https://github.com/ > rmannibucau> | > LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory > <https://javaeefactory-rmannibucau.rhcloud.com> > > 2017-

Dependencies of jstl implementation 1.2.5

Hello, I noticed that the current jstl implementation in TomEE master - taglibs-standard-jstlel-1.2.5.jar - has dependencies to xalan 2.7.1. It is declared as provided in its pom.xml, but in TomEE distribution it is not included. Without it some scenarios throw NoClassDefFound exceptions for

javax.validation API

Hello, TomEE 7 includes javax.validation 1.1 API. However, I noticed, that it's missing some methods from the spec, namely: javax.validation.metadata.CrossParameterDescriptor.getElementClass() javax.validation.metadata.ExecutableDescriptor.findConstraints()

Re: javax.validation API

://rmannibucau.wordpress.com> | Github <https://github.com/ > rmannibucau> | > LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory > <https://javaeefactory-rmannibucau.rhcloud.com> > > 2017-05-25 13:01 GMT+02:00 Lazar Kirchev <lazar.kirc...@gm

PersistenceUnitUtil.getIdentifier() throws a NPE

Hello, I noticed that in TomEE Plume if PersistenceUnitUtil.getIdentifier() is called before any persistence operation is performed, it throws a NullPointerException. This happens because in EclipseLink PersistenceUnitUtil.getIdentifier() uses an object which gets initialized upon entity manager

Missing xalan library in TomEE 7.0.7 and 7.0.8

Hello, About three years ago, xalan library was added to TomEE following https://issues.apache.org/jira/browse/TOMEE-2113 Now in TomEE 7.0.7 this library was removed with https://github.com/apache/tomee/commit/8ab6bb2fb78dd8818c8b330a16687015f4719c5e although the apache taglibs.* 1.2.5 are still

Re: CXF version in TomEE 7.x

those features of CXF > are not used by TomEE itself. Your application may be using them, but if it > is, its likely not portable between Java EE servers and quite tightly > coupled to CXF. > > All this being said, this thread has given me an idea - I'll experiment > with it a

Re: CXF version in TomEE 7.x

Hello, Any update on this? Thanks, Lazar On Fri, Jun 12, 2020 at 9:26 AM Lazar Kirchev wrote: > Hello, > > Both TomEE 7.0.x and TomEE 7.1.x latest versions ship with CXF version > 3.1.18. However, CXF 3.1.x is not supported anymore and version 3.1.18 > (which is the la

CXF version in TomEE 7.x

Hello, Both TomEE 7.0.x and TomEE 7.1.x latest versions ship with CXF version 3.1.18. However, CXF 3.1.x is not supported anymore and version 3.1.18 (which is the last one) is from beginning of 2019 and has security vulnerabilities (e.g. https://nvd.nist.gov/vuln/detail/CVE-2019-12423 and