I'm afraid this is not a 'claning-up' issue because I'm talking about
portability on PHYSICAL artefacts.
You should consider I'm just describing evidence-based facts.
Lets go for some scientific experience :
1) Build the wars with Maven from the git ub repository.
2) Put them in JBoss 7.1 = OK
Hi,
Thanks for pointing the portability issue.
Even if Java EE tends to be more and more portable there are still lots of
areas where there is misunderstanding in regards to the spec meaning.
And sometime there is also no enough information to get a feature
implemented the same way anywhere.
i said you i made it working and i explained you how (that's scientifically
enough since you can reproduce it)
TomEE respects java classloading in this case (not other servers) so you
have to respect it too
if you don't want to respect it go with others, that's not an issue
*Romain Manni-Bucau*
Hi,
please ensure it is not defined in web.xml
if it is nto the case can be an issue of 1.5.2 fixed on trunk
*Romain Manni-Bucau*
*Twitter: @rmannibucau https://twitter.com/rmannibucau*
*Blog: **http://rmannibucau.wordpress.com/*http://rmannibucau.wordpress.com/
*LinkedIn:
Thanks for the quick answer but it seems I didn't explain my situation
completely.
We use Maven for all assignments, I can control what base project they
have to use for a specific assignment. Also in my testsuite I
automatically build these projects and deploy the artifacts to my
embedded
Hi Romain,
I have checked/searched and manually inspected the code. The error happens
to every single servlet in the codebase. There are definitely no duplicate
entries for these servlets in web.xml or web-fragment.xml.
I read around the net, some folks are saying there might be a collision
There is a potential case if you have rest/soap services with your servlets
Jean-Louis
2013/4/24 ronkol rkolias-consult...@scholastic.com
Hi Romain,
I have checked/searched and manually inspected the code. The error happens
to every single servlet in the codebase. There are definitely no
Ah, interesting. We DO have lots of jax-rs rest services. I did not check for
a mapping to /* on those. I will investigate whether we have a rest service
mapped to /* or similar.
--
View this message in context:
Hi guys, I downloaded the latest 1.5.3 snapshot and this issue still occurs
:( Same exact error so I don't think it is resolved.
I have searched all through our code and cannot find any jax-rs service
mapped to /*. We do have servlet FILTERS mapped to /* but servlet filters
are designed to be
Ok, got it. I downloaded the latest 1.6.0 snapshot just now, same error, no
change.
I also noticed tomee is no longer picking up or outputting any logging into
to log4 that used to be caught with the openejb.log.factory=log4j setting,
no longer see:
INFO: Using 'openejb.log.factory=log4j'
So
No you definitely aren't!
Any chance you could share something to reproduce?
Le 24 avr. 2013 18:04, ronkol rkolias-consult...@scholastic.com a
écrit :
Ok, got it. I downloaded the latest 1.6.0 snapshot just now, same error, no
change.
I also noticed tomee is no longer picking up or outputting
well the snapshot is not up to date because of an in progress issue with
the CI system
*Romain Manni-Bucau*
*Twitter: @rmannibucau https://twitter.com/rmannibucau*
*Blog: **http://rmannibucau.wordpress.com/*http://rmannibucau.wordpress.com/
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
Try injecting it this way:
@Inject
@Named(socialAuth)
private SocialAuth socialAuth;
On Wed, Apr 24, 2013 at 1:47 PM, Luca Merolla luca.mero...@gmail.comwrote:
H
ello everyone,
I'm having problem to make socialauth (
https://code.google.com/p/socialauth/)
work in TomEE.
I'm using the
Hi,
The build from https://github.com/skay2k/ejblookup
may be downloaded from
http://ge.tt/5KGXOye?c
ejblookup-engine.war
ejblookup-ui.war
hit
http://localhost:8080/ejblookup-ui/
and check out with different JEE6 AS.
BR
--
View this message in context:
14 matches
Mail list logo
