On 18/05/2014 15:58, Mark Struberg wrote:
Well, not sure it has to do with it, but since 7.0.53 I get a MethodNotFound
in a project which used to work since years if the EL has a null parameter:
This is a question for the users list.
It is a known issue in 7.0.53:
Well, not sure it has to do with it, but since 7.0.53 I get a MethodNotFound in
a project which used to work since years if the EL has a null parameter:
java.lang.NoSuchMethodException:
de.jaxenter.eesummit.caroline.gui.beans.Menu$$OwbNormalScopeProxy0.activateMenuItem(null)
+1
we already talked a bit about it and thought geronimo/specs was the
place but another project could work too.
My goal is mainly to get something consistent.
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Hello guys,
Hope I didnt miss a thread dealing with it, if so please just redirect me.
Tomcat made the choice to do its own API jars. That's not a big deal
by itself but wonder why not putting them with all EE api jars of
Apache, ie in geronimo specs subproject:
On 16/05/2014 07:59, Romain Manni-Bucau wrote:
Hello guys,
Hope I didnt miss a thread dealing with it, if so please just redirect me.
Tomcat made the choice to do its own API jars. That's not a big deal
by itself but wonder why not putting them with all EE api jars of
Apache, ie in
Hi
svn copy would be at least a nice solution to avoid kind of forks
For sure would be great to aligned it both impl. I think geronimo is
the place since most of project are using these APIs (tomee, openejb,
openwebbeans, bval, jcs soon, openjpa, ...)
about the bug the type parameter resolution
My recollection of history (no doubt biased and inaccurate)….
Geronimo originally needed maven-accessible and plausibly maven-metadata'd
jars, and tomcat was extremely maven-unfriendly at the time (and wasn't set up
to easily consume maven artfiacts). I think we (geronimo) copied the first one
