right, just meant the affected versions are all previous ones and
upgrade work was done.
Romain Manni-Bucau
@rmannibucau | Blog | Old Blog | Github | LinkedIn
2017-11-23 16:33 GMT+01:00 COURTAULT Francois :
> Hello,
>
> Romain if I may: TomEE 7.0.4 relies on Tomcat 8.5.20 and not 8.5.23.
>
> Be
Hello,
Romain if I may: TomEE 7.0.4 relies on Tomcat 8.5.20 and not 8.5.23.
Best Regards.
-Original Message-
From: Romain Manni-Bucau [mailto:rmannibu...@gmail.com]
Sent: jeudi 23 novembre 2017 16:28
To: users@tomee.apache.org
Subject: Re: Tomee install issue
It is fixed in the 8.5.23 (
2017-11-23 16:25 GMT+01:00 COURTAULT Francois :
> Romain,
>
> My interceptor is linked to an annotation and is declared in the beans.xml
> in order to work so I guess it is a cdi interceptor and, according to what
> you have said, a new proxy is created and so the injection is not done on the
>
It is fixed in the 8.5.23 (https://tomcat.apache.org/security-8.html)
which is the current tomee version
Romain Manni-Bucau
@rmannibucau | Blog | Old Blog | Github | LinkedIn
2017-11-23 16:21 GMT+01:00 Matthew Broadhead :
> doesn't redhat use an old version of tomcat? last time i installed fro
Romain,
My interceptor is linked to an annotation and is declared in the beans.xml in
order to work so I guess it is a cdi interceptor and, according to what you
have said, a new proxy is created and so the injection is not done on the right
proxy, right ?
But, in this case, is it a bug ?
Th
doesn't redhat use an old version of tomcat? last time i installed from
yum it was really out of date so i installed latest manually. are you
sure this applies to tomee?
On 23/11/2017 16:18, dkwakkel wrote:
The latest CVE is of priority HIGH:
https://access.redhat.com/security/cve/cve-2017-12
The latest CVE is of priority HIGH:
https://access.redhat.com/security/cve/cve-2017-12617.
Are tomcat vulnerabilities monitored and how is decided if a release will be
made? In my opinion every HIGH vulnerability should result in a
fixpack/release. If I can be of any help in this subject please let
annotation = cdi interceptor? if so it leads to a proxy and the
injection happens on the wrong instance I think
Romain Manni-Bucau
@rmannibucau | Blog | Old Blog | Github | LinkedIn
2017-11-23 15:50 GMT+01:00 COURTAULT Francois :
> Hello Romain,
>
> I think I have found the issue.
> In fact, we
Hello Romain,
I think I have found the issue.
In fact, we used a custom annotation for a logging interceptor which targets
METHOD and TYPE.
If we remove this annotation on our WS endpoint (eg TYPE target) , then the
injection is resolved.
Do you know why we have this side effect ? Is it a bu
Looks close to
https://github.com/apache/tomee/blob/master/server/openejb-cxf/src/test/java/org/apache/openejb/server/cxf/PojoWebServiceContextTest.java
, what can be the difference?
Romain Manni-Bucau
@rmannibucau | Blog | Old Blog | Github | LinkedIn
2017-11-23 13:49 GMT+01:00 COURTAULT Fran
Hello,
No it's not an EJB webservice, just a POJO webservice annotated with
@WebService(name = "MyManager", targetNamespace = "http://xxx.yyy.test..com/";,
serviceName = "MyManager", wsdlLocation = "wsdl/MyManager.wsdl") like in the
sample of my first email.
It looks quite similar to the sampl
Hi François,
did you test with an EJB webservice?
Romain Manni-Bucau
@rmannibucau | Blog | Old Blog | Github | LinkedIn
2017-11-23 12:11 GMT+01:00 COURTAULT Francois :
> Hello,
>
> I have the following :
>
> @WebService(name = "MyManager", targetNamespace =
> "http://xxx.yyy.test..com/";, ser
Hello,
I have the following :
@WebService(name = "MyManager", targetNamespace = "http://xxx.yyy.test..com/";,
serviceName = "MyManager", wsdlLocation = "wsdl/MyManager.wsdl")
public class MyManagerService implements MyManager {
@Resource
WebServiceContext webServiceContext;
}
And
13 matches
Mail list logo
