I have a ClientRequestFilter I use for logging entity info using:
// Set up web client with logging filter
final Client client =
ClientBuilder.newClient().register(ClientRequestLoggingFilter.class);
How do you register your ContainerResponseFilter on the server side? Is
there a difference with
I've tried it in a scratch environment with 4.7.2 and it works quite happily
with absolutely no effort and no additional configuration.
Which is sort of irritating as the main environment that I'm using can't be
update for various reasons too frustrating to mention.
The 4.6.0.2 environment a
All the openejb dependencies including openejb-cxf-* are the same 4.6.0.2
version.
Are there any additional outputs I could be looking at? I checked the linked
github example project, it has no web deployment config files, web.xmls etc
and code wise looks identical to what I have.
--
View this
I would suggest you to try the 4.7.2 and if you still have the issue share
a project on github to let us reproduce it.
Romain Manni-Bucau
@rmannibucau https://twitter.com/rmannibucau | Blog
http://rmannibucau.wordpress.com | Github https://github.com/rmannibucau |
LinkedIn
Thanks for input, Romain.
I've started to check something out.
A few of my beans are using omnifaces @viewscope and I see a few cdi
warnings in my logs.
eks: OpenEJB.cdi - Could NOT lazily initialize session context because of
null RequestContext
Reverting back to ViewAccessScope these
Surely a classloader issue. Normally we enrich the classloader with this
jar but you are using a custom classloader so it is surely ignored. So
solution is to use the spring way: all in the app.
Le 6 août 2015 11:34, Mike Spencer mspen...@denniskirk.com a écrit :
Also, when I copy/pasted the
we got several fixes since 4.6.0.2 so can be a bug, do you care testing on
localhost/some-webapp-name-but-not-root just to sanity check the instance
is properly setup
Romain Manni-Bucau
@rmannibucau https://twitter.com/rmannibucau | Blog
http://rmannibucau.wordpress.com | Github
Late reply, but it appears that you are using the same interface. I
copy/pasted the 4.7.2 version of OpenEJBServerPlatform
http://grepcode.com/file/repo1.maven.org/maven2/org.apache.openejb/openejb-jpa-integration/4.7.2/org/apache/openejb/jpa/integration/eclipselink/OpenEJBServerPlatform.java/
Also, when I copy/pasted the OpenEJBServerPlatform class into my project
and used that, the transactions started working. So it seems like if I
use the correct eclipselink.target-server property transactions are
working. Now I just need to figure out why it isn't being found when
using the
Can you check your dependencies versions? Ie dont mix up cxf and openejb
versions for instance.
Le 6 août 2015 01:18, Temeraire a.p.ri...@gmail.com a écrit :
No. This is the full extent of the error message in the openejb-init.log.
Which is the only file specified in the logging.properties
No. This is the full extent of the error message in the openejb-init.log.
Which is the only file specified in the logging.properties file. The logging
level is set to info, but changing to Debug doesn't show any more data.
--
View this message in context:
11 matches
Mail list logo
