I never got this working all my ITs are broken. :-(
On Fri, Dec 16, 2016 at 6:53 PM, alexdron wrote:
> Romain,
> Do you know if that was resolved?
>
> I have a similar issue. Jackson provider v2.1.5 was working perfectly fine
> along with Tomee Plus 7.0.1 until we
Romain,
Do you know if that was resolved?
I have a similar issue. Jackson provider v2.1.5 was working perfectly fine
along with Tomee Plus 7.0.1 until we upgraded jackson-jaxrs-json-provider to
version 2.8.5. And for some reason it is not picked anymore by CXF.
We extend JacksonJaxbJsonProvider
Hi Romain,
thanks for the answer, I should have thought about the rules ordering.
Normally, I always use RuleChain when I write my own tests, but for once, I
took an existing test
Hi Xavier,
first test doesnt pass cause app composer runs the test as an EJB
(ManagedBean actually) and therefore inherits from the auto request scope
for it. RequestScoped is quite particular cause often implicit so switching
it off is quite an issue for a lot of tests - it explains why it is
Hi,
I have a problem with the following test (with TomEE 7.0.1):
@ContainerProperties(@ContainerProperties.Property(name =
"openejb.testing.start-cdi-contexts", value = "false"))
@Classes(cdi = true, innerClassesAsBean = true)
@RunWith(ApplicationComposer.class)
public class ScopesRuleTest {
It seems like the problem is due to our reverse proxy, NGINX, which return a
504 error after the "upstream timed out".
I'll reply to myself when I'll find the right configuration.
;-)
--
View this message in context:
https://tomcat.apache.org/tomcat-7.0-doc/config/filter.html#CORS_Filter
On 15 December 2016 at 19:34, Romain Manni-Bucau
wrote:
> Hi
>
> there are a lot of option but if you use a standalone instance tomcat cors
> filter is a good one.
>
>
> Romain Manni-Bucau
>