cxf interceptors in 2.0 api

Hi, does anyone know if it's possible to use cxf interceptors in jax-rs 2.0 client API in tomee 7? ex LoggingOutInterceptor. WebClient usage is obviously ok, /hw -- View this message in context: http://tomee-openejb.979440.n4.nabble.com/cxf-interceptors-in-2-0-api-tp4680333.html Sent from

Re: cxf interceptors in 2.0 api

Hi, yep, That's what I found out aswell, but feature was what I was looking for. Thx, hw -- View this message in context: http://tomee-openejb.979440.n4.nabble.com/cxf-interceptors-in-2-0-api-tp4680333p4680335.html Sent from the TomEE Users mailing list archive at Nabble.com.

Re: cxf interceptors in 2.0 api

Hi we purely rely on cxf for that so that's more a cxf question. I know cxf features (org.apache.cxf.feature.Feature) have been wired on the jaxrs client API (I often use the old loggingfeature). I only checked org.apache.cxf.jaxrs.client.spec.ClientImpl.WebTargetImpl#request() but I don't think

Re: Cannot create a secure XMLInputFactory

OK, I've built TomEE from source before, but I've not run it in debug mode. Wouldn't it be just as easy to simply log vars f, p and o when I build the source? On Mon, Oct 17, 2016 at 5:09 PM, Romain Manni-Bucau wrote: > cxf ones yes, that's as easy as adding cxf-core as

Re: Cannot create a secure XMLInputFactory

~/java/apache-maven-3.3.9/bin/mvn dependency:tree | egrep 'woo|xml|stax' [INFO] | | +- javax.xml.bind:jaxb-api:jar:2.2.6:test [INFO] | | \- com.sun.xml.bind:jaxb-impl:jar:2.2.6:test [INFO] | | | +- org.apache.santuario:xmlsec:jar:2.0.5:test [INFO] | | | | | +-

Local EJB security

Hi, I have RESTful web service @Path("/education") public class EducationRest { @EJB private EducationBean service; @GET @Path("/readAll") @Produces({MediaType.APPLICATION_XML, MediaType.APPLICATION_JSON})

Re: cxf interceptors in 2.0 api

BTW, not sure if this is a cxf or tomee issue, but I've noticed something strange. I'm invoking an async client and if I register the loggingfeature it prints out two response, one with payload, the other without. Like this: ID: 1 Address: https://myapi/service Http-Method: POST Content-Type:

Re: cxf interceptors in 2.0 api

The 2 lines before you copy/paste would be interesting as well. Can be a lot of things like - bad logging config - server and client logs being mixed - feature being added twice - ... You can put a breakpoint in the in interceptor and check it is or not the same instance maybe. Le 17 oct. 2016

Re: JSP named bean bug

Hi Just I tried with 7.0.2-SNAPHOT and it works perfectly :) Best Gurkan Erdogdu http://twitter.com/gerdogdu http://managecat.com > On 17 Oct 2016, at 17:47, tonywestonuk wrote: > > There... pretty straight forward. >

Re: JSP named bean bug

which version does it affect? can you build a project on github ready to run showing that (an arquillian test or tomee-maven-plugin setup are good way to share it)? Romain Manni-Bucau @rmannibucau | Blog | Old Wordpress

Re: JSP named bean bug

There... pretty straight forward. https://github.com/tonywestonuk/tomeebug It affects 7.0.1 -- View this message in context: http://tomee-openejb.979440.n4.nabble.com/JSP-named-bean-bug-tp4680338p4680342.html Sent from the TomEE Users mailing list archive at Nabble.com.

Re: JSP named bean bug

Hi Ok got it now, comes from a change in tomcat backbone, I fixed it on 7.0.2 snapshot the trick is to preload JasperInitializer before any deployment of that kind. That is why it works from the second deployment, cause this initializer was executed. Romain Manni-Bucau @rmannibucau

Re: JSP named bean bug

Great! Thanks Is there a workaround I can use for 7.0.1, or should I wait until you release 7.0.2 I don't fancy building 7.0.2 myself :-/ Thanks. -- View this message in context: http://tomee-openejb.979440.n4.nabble.com/JSP-named-bean-bug-tp4680338p4680346.html Sent from the TomEE

Re: JSP named bean bug

Do you have a link to 7.0.2-snapshot, or do I have to build it myself? -- View this message in context: http://tomee-openejb.979440.n4.nabble.com/JSP-named-bean-bug-tp4680338p4680344.html Sent from the TomEE Users mailing list archive at Nabble.com.

Re: JSP named bean bug

Hi does it work in a standalone tomee (= not using WTP or eclipse at all)? Romain Manni-Bucau @rmannibucau | Blog | Old Wordpress Blog | Github |

Re: JSP named bean bug

It happens on stand alone. Indeed I found this bug when my application doesn't work if you restart the live server, only if you restart it, and then deploy a new version of the app.which confused the hell out of me to begin with! Thanks. -- View this message in context:

JSP named bean bug

Hi. I think i've fallen fowl of a bug Let me outline the steps to reproduce. 1) Create an application scoped bean @ApplicationScoped @Named("bugbean") public class BugBean { public String getBugVal(){ return "bugval"; } } 2) Create a JSP to show it. <%@ page

Cannot create a secure XMLInputFactory

Periodically I'm seeing "Cannot create a secure XMLInputFactory" in TomEE 7.0.2-SNAPSHOT. One solution is for CXF using -Dorg.apache.cxf.stax.allowInsecureParser=1. This is an older 7.0.2 from 7/4/16. -- View this message in context:

Re: JSP named bean bug

Hi Romain, Yay! All working in 7.0.2-snapshot. Thank you for such a fast response, and your ongoing support. Tony. -- View this message in context: http://tomee-openejb.979440.n4.nabble.com/JSP-named-bean-bug-tp4680338p4680350.html Sent from the TomEE Users mailing list archive at

Re: Cannot create a secure XMLInputFactory

My compile dependencies are (do you see anything that sticks out): org.jsr107.ri cache-annotations-ri-cdi 1.0.0 org.jvnet.jaxb2_commons jaxb2-basics-runtime 0.10.0

Re: JSP named bean bug

snapshot is there https://repository.apache.org/content/repositories/snapshots/org/apache/tomee/apache-tomee/7.0.2-SNAPSHOT/ a dirty but which should work workaround is to add a class in your app which does in a static block a Class.forName() of JasperInitializer: Class.

Re: Cannot create a secure XMLInputFactory

Hello can happen if you provide some xml libraries in your app - like woodstox or stax*api - and it conflicts at some point. Romain Manni-Bucau @rmannibucau | Blog | Old Wordpress Blog |

Re: Cannot create a secure XMLInputFactory

OK, I made the following change and I still get the error: org.jvnet.jaxb2_commons jaxb2-basics-runtime 0.10.0 provided I even tried: org.apache.tomee tomee-jaxrs ${tomee.version}

Re: Cannot create a secure XMLInputFactory

I need JAX-B runtime for code generated by jaxws-maven-plugin and XJC. Everything else is in test scope and not used in the deployed app. org.jvnet.jaxb2_commons jaxb2-basics-runtime 0.10.0 On Mon, Oct 17, 2016 at 1:57 PM, Romain Manni-Bucau

Re: Cannot create a secure XMLInputFactory

well jaxb is provided and shouldnt be delivered so you have to remove it from WEB-INF/lib. scope=provided should be fine too. Romain Manni-Bucau @rmannibucau | Blog | Old Wordpress Blog |

Re: Cannot create a secure XMLInputFactory

If you can put a breakpoint at https://github.com/apache/cxf/blob/eab841d5477c5e1ed21a49918defa79a0f1ad533/core/src/main/java/org/apache/cxf/staxutils/StaxUtils.java#L381 then you would know immediately why the throwable is thrown. Romain Manni-Bucau @rmannibucau

Re: Cannot create a secure XMLInputFactory

You mean set a breakpoint in TomEE source? On Mon, Oct 17, 2016 at 4:43 PM, Romain Manni-Bucau wrote: > If you can put a breakpoint at > https://github.com/apache/cxf/blob/eab841d5477c5e1ed21a49918defa7 >

Re: Cannot create a secure XMLInputFactory

cxf ones yes, that's as easy as adding cxf-core as provded dependency, putting a breakpoint on the mentionned line normally and starting tomee in debug mode. Surely the most efficient way to solve it. Romain Manni-Bucau @rmannibucau | Blog