I wouldn't add it in the container (cxf is a special jar for tomee
plus) but giving a try is the best way to know ;). Wonder if you can't
simply use cxf 3/2.7 async conduit with cxf 2. It is theorytically
possible, would need to check the modularity of cxf for it.
Romain Manni-Bucau
Twitter:
Hu and add it to TomEE Web Profile? there is no previous apache cxf, of
course you will loose security integration or integration to other modules,
but as if you were using Tomcat, and then when TomEE 2.0.0 is released,
user can switch directly.
2014-07-17 8:40 GMT+02:00 Romain Manni-Bucau
@Alex: Anthony said he is using plus distrib so not an option actually :(
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-07-17 8:43 GMT+02:00 Alex Soto
Thanks,
WEB-INF/persistence.xml works.
Right after getting this work, i've run into another problem
I get an error from liquibase.
Error Reading Migration File: Found 2 files that match changelog.xml
Just for the enhancement in the future: Any file in resources can cause a
similar problem.
Yes, that's the fix to do. Hopefully tonight on trunk (then don't know
if it will be mergeable with 1.7 or too late)
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
We can probably merge for a 1.7.1 I think.
Not really a big deal and we should get more feedback from users that
requires a maintenance release.
JLouis
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Thu, Jul 17, 2014 at 10:12 AM, Romain Manni-Bucau
yep that's the open point, I can't fix it now ($dayjob) but not a
blocking for a release since that's something new and still a bit
experimental (but I'm already addicted ;)).
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn:
lol
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Thu, Jul 17, 2014 at 10:20 AM, Romain Manni-Bucau rmannibu...@gmail.com
wrote:
yep that's the open point, I can't fix it now ($dayjob) but not a
blocking for a release since that's something new and
Thank you guys, even me agree it is not a blocker bug.
Romain: I don't want to be the man who force you work at midnight :)
I've hacked liquibase. Overridden a method not to fail when
classLoader.getResources(path) returns more element.
Now it works.
But i've run into an other problem :P
Thanks for sharing
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Thu, Jul 17, 2014 at 12:41 PM, Tamás Kimmel kumm0...@gmail.com wrote:
Yes, tried moving it, and leaving in resources too.
Eclipselink does not log an exact path where is it looking for
hmm, looked a bit and fixing it for mvn plugin would introduce side
effects in other usages (where you want it). Actually it means the war
shouldn't take into account these resources. This is not what does
default config but it can be done with some more config.
I'll let it this way for next
I think the current behavior should be left alone. If you have an
Apache Maven multi-module project where you are putting different
persistence.xml units for different modules, then you should exclude
them from the final artifact for those intermediary modules. Both
m-jar-p and m-war-p support
Romain Manni-Bucau wrote
Wonder if you can't
simply use cxf 3/2.7 async conduit with cxf 2. It is theorytically
possible, would need to check the modularity of cxf for it.
I'll try this approach.
I have another question related to this. I'm performing the webservice
invokeAsync calls from
No but deltaspike BeanProvider can help ;)
Le 17 juil. 2014 23:13, Anthony Fryer apfr...@hotmail.com a écrit :
Romain Manni-Bucau wrote
Wonder if you can't
simply use cxf 3/2.7 async conduit with cxf 2. It is theorytically
possible, would need to check the modularity of cxf for it.
I'll
14 matches
Mail list logo
