You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomee.apache.org by Berner Martin <Ma...@qualitasag.ch> on 2014/08/22 11:37:55 UTC
Application stop working with by switching from TomEE 1.6.0 to
1.6.0.1
Hi all
I have a EL problem since new Versions of TomEE are based on Tomcat 7.0.53. Problem depends on a Fix in jasper-el.jar.
When org.apache.el.parser.AstValue.getValue calls javax.el.BeanELResolver.invoke(ELContext context, Object base, Object method, Class<?>[] paramTypes, Object[] params)
In Version before Tomcat 7.0.53 the Value paramTypes was null in my situation. With 7.0.53 the value is an Array with one null Entry.
The invoke try to find an appropriate Method by looping over all Methods when paramTypes is null put now it isn't! So it works different and fails with a NoSuchMethodException.
Is there anyone who has similar Problems or any Hints, Fixes, Workarounds?
Any Help is appreciated.
Best regards
Martin Berner
AW: Application stop working with by switching from TomEE 1.6.0 to
1.6.0.1
Posted by Berner Martin <Ma...@qualitasag.ch>.
Hi Romain,
Get my LazyRealm to work whith this code:
package ch.qual.base.app.realm;
import org.apache.catalina.LifecycleException;
import org.apache.catalina.LifecycleState;
public class MyLazyRealm extends org.apache.tomee.catalina.realm.LazyRealm {
private static final String REALM_INFO = MyLazyRealm.class.getName() + "/1.0";
@Override
protected void initInternal() throws LifecycleException {
}
@Override
protected void startInternal() throws LifecycleException {
setState(LifecycleState.STARTING);
}
@Override
public String getInfo() {
return REALM_INFO;
}
@Override
protected void stopInternal() throws LifecycleException {
setState(LifecycleState.STOPPING);
}
}
We need to get the real Realm to be initiated as late as possible. Optimizli at first Request..
Coming back to my Initial Problem with jasper-el.jar. My App is working on TomEE 1.7.0 without replacing jasper-el from a privieuse Version.
Tested on TomEE JAXRS 1.7.0 and TomEE PLUME 1.7.0
Martin
-----Ursprüngliche Nachricht-----
Von: Romain Manni-Bucau [mailto:rmannibucau@gmail.com]
Gesendet: Dienstag, 26. August 2014 07:28
An: users@tomee.apache.org
Betreff: Re: Application stop working with by switching from TomEE 1.6.0 to 1.6.0.1
it will be backported
you can do your own realm extending this one and overriding init() to skip it (no-op impl).
Not yet sure we target as date for the "1.7.0+1"
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-08-26 7:13 GMT+02:00 Berner Martin <Ma...@qualitasag.ch>:
> Hi Romain
> Thanks for opening a Bug on that.
> It is Fixed on 2.0.0?
> Is it possible or even planed to fix this on Version 1.7?
>
> We do a lot of CDI stuff in the lazy loaded Realm (ch.qual.base.app.realm.ContextDatabaseRealm) so it would be realy nice if it would be CDI-Managed. Do I have to make a own Lazy Realm in between of the LazyRealm and our own to load the CDI Realm later?
>
> Martin Berner
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Romain Manni-Bucau [mailto:rmannibucau@gmail.com]
> Gesendet: Montag, 25. August 2014 18:54
> An: users@tomee.apache.org
> Betreff: Re: Application stop working with by switching from TomEE
> 1.6.0 to 1.6.0.1
>
> Hi
>
> https://issues.apache.org/jira/browse/TOMEE-1334 should help
>
> PS: without activating CDI it should work
>
>
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
>
>
> 2014-08-25 16:04 GMT+02:00 Berner Martin <Ma...@qualitasag.ch>:
>> Hi Romain,
>> Application doesn't start under 1.7.0 because of a NullPointerException with a LazyRealm.
>>
>> This is declaration in context.xml:
>> <Realm className="org.apache.tomee.catalina.realm.LazyRealm"
>> realmClass="ch.qual.base.app.realm.ContextDatabaseRealm"
>> cdi="true" />
>>
>> And that’s the Logg by starting Application:
>>
>> Schwerwiegend: A child container failed during start
>> java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/MilkSheepWeb]]
>> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
>> at java.util.concurrent.FutureTask.get(FutureTask.java:188)
>> at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:1123)
>> at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:816)
>> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>> at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1575)
>> at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1565)
>> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>> at java.lang.Thread.run(Thread.java:724)
>> Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/MilkSheepWeb]]
>> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
>> ... 6 more
>> Caused by: org.apache.catalina.LifecycleException: Failed to initialize component [org.apache.tomee.catalina.realm.LazyRealm@4946ed22]
>> at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:106)
>> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139)
>> at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5373)
>> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>> ... 6 more
>> Caused by: java.lang.NullPointerException
>> at org.apache.tomee.catalina.realm.LazyRealm.instance(LazyRealm.java:106)
>> at org.apache.tomee.catalina.realm.LazyRealm.initInternal(LazyRealm.java:130)
>> at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
>> ... 9 more
>>
>>
>> Martin Berner
>>
>>
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Berner Martin [mailto:Martin.Berner@qualitasag.ch]
>> Gesendet: Freitag, 22. August 2014 13:51
>> An: 'users@tomee.apache.org'
>> Betreff: AW: Application stop working with by switching from TomEE
>> 1.6.0 to 1.6.0.1
>>
>> Hi Romain
>> get it to work by copying the jasper-el.jar from 1.6.0 to the lib of CATALINA_HOME (confound the Variables in last Explanation) and running with TomEE 1.6.0.2.
>> No success with 1.7.0 but wit on other Issue. (Nullpointer Exception). But no Time to trace this Issue down at the moment.
>> Let you know if I had news to that.
>>
>> Martin
>>
>>
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Romain Manni-Bucau [mailto:rmannibucau@gmail.com]
>> Gesendet: Freitag, 22. August 2014 13:33
>> An: users@tomee.apache.org
>> Betreff: Re: Application stop working with by switching from TomEE
>> 1.6.0 to 1.6.0.1
>>
>> If you have 5mn would be great to get your feedback on 1.7.0. I
>> remember I did something about it but can't find back which version
>> (1.7 or trunk).
>>
>>
>> Romain Manni-Bucau
>> Twitter: @rmannibucau
>> Blog: http://rmannibucau.wordpress.com/
>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
>> Github: https://github.com/rmannibucau
>>
>>
>> 2014-08-22 13:28 GMT+02:00 Berner Martin <Ma...@qualitasag.ch>:
>>> Hi Romain
>>> I had replaced the jar which solves the Problem. I had Multiple CATALINA_BASE with same CATALINA_HOME not any of the Application are affected so I don’t like to replace the jar at CATALINA_HOME. But I'll try to put it in lib of CATALINA_BASE for the Instances with affected Applications.
>>>
>>> I stumble over the Problem when I tried to switch from 1.6.0 to 1.6.0.2. Lot of debugging searching and pain later I realised, that it even don’t work on 1.6.0 1 and get the major hint in changelog (change of Tomcatversion 7.0.51 -> 7.0.53). Didn't try the 1.7.0 but it is based on Tomcat 7.0.53 too so maybe there is the same Problem.
>>>
>>> Best regards
>>> Martin Berner
>>>
>>> -----Ursprüngliche Nachricht-----
>>> Von: Romain Manni-Bucau [mailto:rmannibucau@gmail.com]
>>> Gesendet: Freitag, 22. August 2014 13:07
>>> An: users@tomee.apache.org
>>> Betreff: Re: Application stop working with by switching from TomEE
>>> 1.6.0 to 1.6.0.1
>>>
>>> Hi
>>>
>>> IIRC you can replace this jar
>>>
>>> BTW did you really wanted to say 1.6.0.1? isn't it 1.6.0.2 or 1.7.0?
>>>
>>>
>>> Romain Manni-Bucau
>>> Twitter: @rmannibucau
>>> Blog: http://rmannibucau.wordpress.com/
>>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
>>> Github: https://github.com/rmannibucau
>>>
>>>
>>> 2014-08-22 11:37 GMT+02:00 Berner Martin <Ma...@qualitasag.ch>:
>>>> Hi all
>>>> I have a EL problem since new Versions of TomEE are based on Tomcat 7.0.53. Problem depends on a Fix in jasper-el.jar.
>>>>
>>>> When org.apache.el.parser.AstValue.getValue calls
>>>> javax.el.BeanELResolver.invoke(ELContext context, Object base,
>>>> Object method, Class<?>[] paramTypes, Object[] params)
>>>>
>>>> In Version before Tomcat 7.0.53 the Value paramTypes was null in my situation. With 7.0.53 the value is an Array with one null Entry.
>>>> The invoke try to find an appropriate Method by looping over all Methods when paramTypes is null put now it isn't! So it works different and fails with a NoSuchMethodException.
>>>>
>>>> Is there anyone who has similar Problems or any Hints, Fixes, Workarounds?
>>>>
>>>> Any Help is appreciated.
>>>>
>>>> Best regards
>>>> Martin Berner
Re: Application stop working with by switching from TomEE 1.6.0 to 1.6.0.1
Posted by Romain Manni-Bucau <rm...@gmail.com>.
it will be backported
you can do your own realm extending this one and overriding init() to
skip it (no-op impl).
Not yet sure we target as date for the "1.7.0+1"
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-08-26 7:13 GMT+02:00 Berner Martin <Ma...@qualitasag.ch>:
> Hi Romain
> Thanks for opening a Bug on that.
> It is Fixed on 2.0.0?
> Is it possible or even planed to fix this on Version 1.7?
>
> We do a lot of CDI stuff in the lazy loaded Realm (ch.qual.base.app.realm.ContextDatabaseRealm) so it would be realy nice if it would be CDI-Managed. Do I have to make a own Lazy Realm in between of the LazyRealm and our own to load the CDI Realm later?
>
> Martin Berner
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Romain Manni-Bucau [mailto:rmannibucau@gmail.com]
> Gesendet: Montag, 25. August 2014 18:54
> An: users@tomee.apache.org
> Betreff: Re: Application stop working with by switching from TomEE 1.6.0 to 1.6.0.1
>
> Hi
>
> https://issues.apache.org/jira/browse/TOMEE-1334 should help
>
> PS: without activating CDI it should work
>
>
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
>
>
> 2014-08-25 16:04 GMT+02:00 Berner Martin <Ma...@qualitasag.ch>:
>> Hi Romain,
>> Application doesn't start under 1.7.0 because of a NullPointerException with a LazyRealm.
>>
>> This is declaration in context.xml:
>> <Realm className="org.apache.tomee.catalina.realm.LazyRealm"
>> realmClass="ch.qual.base.app.realm.ContextDatabaseRealm"
>> cdi="true" />
>>
>> And that’s the Logg by starting Application:
>>
>> Schwerwiegend: A child container failed during start
>> java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/MilkSheepWeb]]
>> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
>> at java.util.concurrent.FutureTask.get(FutureTask.java:188)
>> at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:1123)
>> at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:816)
>> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>> at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1575)
>> at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1565)
>> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>> at java.lang.Thread.run(Thread.java:724)
>> Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/MilkSheepWeb]]
>> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
>> ... 6 more
>> Caused by: org.apache.catalina.LifecycleException: Failed to initialize component [org.apache.tomee.catalina.realm.LazyRealm@4946ed22]
>> at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:106)
>> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139)
>> at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5373)
>> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>> ... 6 more
>> Caused by: java.lang.NullPointerException
>> at org.apache.tomee.catalina.realm.LazyRealm.instance(LazyRealm.java:106)
>> at org.apache.tomee.catalina.realm.LazyRealm.initInternal(LazyRealm.java:130)
>> at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
>> ... 9 more
>>
>>
>> Martin Berner
>>
>>
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Berner Martin [mailto:Martin.Berner@qualitasag.ch]
>> Gesendet: Freitag, 22. August 2014 13:51
>> An: 'users@tomee.apache.org'
>> Betreff: AW: Application stop working with by switching from TomEE
>> 1.6.0 to 1.6.0.1
>>
>> Hi Romain
>> get it to work by copying the jasper-el.jar from 1.6.0 to the lib of CATALINA_HOME (confound the Variables in last Explanation) and running with TomEE 1.6.0.2.
>> No success with 1.7.0 but wit on other Issue. (Nullpointer Exception). But no Time to trace this Issue down at the moment.
>> Let you know if I had news to that.
>>
>> Martin
>>
>>
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Romain Manni-Bucau [mailto:rmannibucau@gmail.com]
>> Gesendet: Freitag, 22. August 2014 13:33
>> An: users@tomee.apache.org
>> Betreff: Re: Application stop working with by switching from TomEE
>> 1.6.0 to 1.6.0.1
>>
>> If you have 5mn would be great to get your feedback on 1.7.0. I
>> remember I did something about it but can't find back which version
>> (1.7 or trunk).
>>
>>
>> Romain Manni-Bucau
>> Twitter: @rmannibucau
>> Blog: http://rmannibucau.wordpress.com/
>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
>> Github: https://github.com/rmannibucau
>>
>>
>> 2014-08-22 13:28 GMT+02:00 Berner Martin <Ma...@qualitasag.ch>:
>>> Hi Romain
>>> I had replaced the jar which solves the Problem. I had Multiple CATALINA_BASE with same CATALINA_HOME not any of the Application are affected so I don’t like to replace the jar at CATALINA_HOME. But I'll try to put it in lib of CATALINA_BASE for the Instances with affected Applications.
>>>
>>> I stumble over the Problem when I tried to switch from 1.6.0 to 1.6.0.2. Lot of debugging searching and pain later I realised, that it even don’t work on 1.6.0 1 and get the major hint in changelog (change of Tomcatversion 7.0.51 -> 7.0.53). Didn't try the 1.7.0 but it is based on Tomcat 7.0.53 too so maybe there is the same Problem.
>>>
>>> Best regards
>>> Martin Berner
>>>
>>> -----Ursprüngliche Nachricht-----
>>> Von: Romain Manni-Bucau [mailto:rmannibucau@gmail.com]
>>> Gesendet: Freitag, 22. August 2014 13:07
>>> An: users@tomee.apache.org
>>> Betreff: Re: Application stop working with by switching from TomEE
>>> 1.6.0 to 1.6.0.1
>>>
>>> Hi
>>>
>>> IIRC you can replace this jar
>>>
>>> BTW did you really wanted to say 1.6.0.1? isn't it 1.6.0.2 or 1.7.0?
>>>
>>>
>>> Romain Manni-Bucau
>>> Twitter: @rmannibucau
>>> Blog: http://rmannibucau.wordpress.com/
>>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
>>> Github: https://github.com/rmannibucau
>>>
>>>
>>> 2014-08-22 11:37 GMT+02:00 Berner Martin <Ma...@qualitasag.ch>:
>>>> Hi all
>>>> I have a EL problem since new Versions of TomEE are based on Tomcat 7.0.53. Problem depends on a Fix in jasper-el.jar.
>>>>
>>>> When org.apache.el.parser.AstValue.getValue calls
>>>> javax.el.BeanELResolver.invoke(ELContext context, Object base,
>>>> Object method, Class<?>[] paramTypes, Object[] params)
>>>>
>>>> In Version before Tomcat 7.0.53 the Value paramTypes was null in my situation. With 7.0.53 the value is an Array with one null Entry.
>>>> The invoke try to find an appropriate Method by looping over all Methods when paramTypes is null put now it isn't! So it works different and fails with a NoSuchMethodException.
>>>>
>>>> Is there anyone who has similar Problems or any Hints, Fixes, Workarounds?
>>>>
>>>> Any Help is appreciated.
>>>>
>>>> Best regards
>>>> Martin Berner
AW: Application stop working with by switching from TomEE 1.6.0 to
1.6.0.1
Posted by Berner Martin <Ma...@qualitasag.ch>.
Hi Romain
Thanks for opening a Bug on that.
It is Fixed on 2.0.0?
Is it possible or even planed to fix this on Version 1.7?
We do a lot of CDI stuff in the lazy loaded Realm (ch.qual.base.app.realm.ContextDatabaseRealm) so it would be realy nice if it would be CDI-Managed. Do I have to make a own Lazy Realm in between of the LazyRealm and our own to load the CDI Realm later?
Martin Berner
-----Ursprüngliche Nachricht-----
Von: Romain Manni-Bucau [mailto:rmannibucau@gmail.com]
Gesendet: Montag, 25. August 2014 18:54
An: users@tomee.apache.org
Betreff: Re: Application stop working with by switching from TomEE 1.6.0 to 1.6.0.1
Hi
https://issues.apache.org/jira/browse/TOMEE-1334 should help
PS: without activating CDI it should work
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-08-25 16:04 GMT+02:00 Berner Martin <Ma...@qualitasag.ch>:
> Hi Romain,
> Application doesn't start under 1.7.0 because of a NullPointerException with a LazyRealm.
>
> This is declaration in context.xml:
> <Realm className="org.apache.tomee.catalina.realm.LazyRealm"
> realmClass="ch.qual.base.app.realm.ContextDatabaseRealm"
> cdi="true" />
>
> And that’s the Logg by starting Application:
>
> Schwerwiegend: A child container failed during start
> java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/MilkSheepWeb]]
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:188)
> at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:1123)
> at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:816)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
> at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1575)
> at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1565)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:724)
> Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/MilkSheepWeb]]
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
> ... 6 more
> Caused by: org.apache.catalina.LifecycleException: Failed to initialize component [org.apache.tomee.catalina.realm.LazyRealm@4946ed22]
> at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:106)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139)
> at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5373)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
> ... 6 more
> Caused by: java.lang.NullPointerException
> at org.apache.tomee.catalina.realm.LazyRealm.instance(LazyRealm.java:106)
> at org.apache.tomee.catalina.realm.LazyRealm.initInternal(LazyRealm.java:130)
> at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
> ... 9 more
>
>
> Martin Berner
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Berner Martin [mailto:Martin.Berner@qualitasag.ch]
> Gesendet: Freitag, 22. August 2014 13:51
> An: 'users@tomee.apache.org'
> Betreff: AW: Application stop working with by switching from TomEE
> 1.6.0 to 1.6.0.1
>
> Hi Romain
> get it to work by copying the jasper-el.jar from 1.6.0 to the lib of CATALINA_HOME (confound the Variables in last Explanation) and running with TomEE 1.6.0.2.
> No success with 1.7.0 but wit on other Issue. (Nullpointer Exception). But no Time to trace this Issue down at the moment.
> Let you know if I had news to that.
>
> Martin
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Romain Manni-Bucau [mailto:rmannibucau@gmail.com]
> Gesendet: Freitag, 22. August 2014 13:33
> An: users@tomee.apache.org
> Betreff: Re: Application stop working with by switching from TomEE
> 1.6.0 to 1.6.0.1
>
> If you have 5mn would be great to get your feedback on 1.7.0. I
> remember I did something about it but can't find back which version
> (1.7 or trunk).
>
>
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
>
>
> 2014-08-22 13:28 GMT+02:00 Berner Martin <Ma...@qualitasag.ch>:
>> Hi Romain
>> I had replaced the jar which solves the Problem. I had Multiple CATALINA_BASE with same CATALINA_HOME not any of the Application are affected so I don’t like to replace the jar at CATALINA_HOME. But I'll try to put it in lib of CATALINA_BASE for the Instances with affected Applications.
>>
>> I stumble over the Problem when I tried to switch from 1.6.0 to 1.6.0.2. Lot of debugging searching and pain later I realised, that it even don’t work on 1.6.0 1 and get the major hint in changelog (change of Tomcatversion 7.0.51 -> 7.0.53). Didn't try the 1.7.0 but it is based on Tomcat 7.0.53 too so maybe there is the same Problem.
>>
>> Best regards
>> Martin Berner
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Romain Manni-Bucau [mailto:rmannibucau@gmail.com]
>> Gesendet: Freitag, 22. August 2014 13:07
>> An: users@tomee.apache.org
>> Betreff: Re: Application stop working with by switching from TomEE
>> 1.6.0 to 1.6.0.1
>>
>> Hi
>>
>> IIRC you can replace this jar
>>
>> BTW did you really wanted to say 1.6.0.1? isn't it 1.6.0.2 or 1.7.0?
>>
>>
>> Romain Manni-Bucau
>> Twitter: @rmannibucau
>> Blog: http://rmannibucau.wordpress.com/
>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
>> Github: https://github.com/rmannibucau
>>
>>
>> 2014-08-22 11:37 GMT+02:00 Berner Martin <Ma...@qualitasag.ch>:
>>> Hi all
>>> I have a EL problem since new Versions of TomEE are based on Tomcat 7.0.53. Problem depends on a Fix in jasper-el.jar.
>>>
>>> When org.apache.el.parser.AstValue.getValue calls
>>> javax.el.BeanELResolver.invoke(ELContext context, Object base,
>>> Object method, Class<?>[] paramTypes, Object[] params)
>>>
>>> In Version before Tomcat 7.0.53 the Value paramTypes was null in my situation. With 7.0.53 the value is an Array with one null Entry.
>>> The invoke try to find an appropriate Method by looping over all Methods when paramTypes is null put now it isn't! So it works different and fails with a NoSuchMethodException.
>>>
>>> Is there anyone who has similar Problems or any Hints, Fixes, Workarounds?
>>>
>>> Any Help is appreciated.
>>>
>>> Best regards
>>> Martin Berner
Re: Application stop working with by switching from TomEE 1.6.0 to 1.6.0.1
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hi
https://issues.apache.org/jira/browse/TOMEE-1334 should help
PS: without activating CDI it should work
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-08-25 16:04 GMT+02:00 Berner Martin <Ma...@qualitasag.ch>:
> Hi Romain,
> Application doesn't start under 1.7.0 because of a NullPointerException with a LazyRealm.
>
> This is declaration in context.xml:
> <Realm className="org.apache.tomee.catalina.realm.LazyRealm"
> realmClass="ch.qual.base.app.realm.ContextDatabaseRealm"
> cdi="true" />
>
> And that’s the Logg by starting Application:
>
> Schwerwiegend: A child container failed during start
> java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/MilkSheepWeb]]
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:188)
> at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:1123)
> at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:816)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
> at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1575)
> at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1565)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:724)
> Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/MilkSheepWeb]]
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
> ... 6 more
> Caused by: org.apache.catalina.LifecycleException: Failed to initialize component [org.apache.tomee.catalina.realm.LazyRealm@4946ed22]
> at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:106)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139)
> at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5373)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
> ... 6 more
> Caused by: java.lang.NullPointerException
> at org.apache.tomee.catalina.realm.LazyRealm.instance(LazyRealm.java:106)
> at org.apache.tomee.catalina.realm.LazyRealm.initInternal(LazyRealm.java:130)
> at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
> ... 9 more
>
>
> Martin Berner
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Berner Martin [mailto:Martin.Berner@qualitasag.ch]
> Gesendet: Freitag, 22. August 2014 13:51
> An: 'users@tomee.apache.org'
> Betreff: AW: Application stop working with by switching from TomEE 1.6.0 to 1.6.0.1
>
> Hi Romain
> get it to work by copying the jasper-el.jar from 1.6.0 to the lib of CATALINA_HOME (confound the Variables in last Explanation) and running with TomEE 1.6.0.2.
> No success with 1.7.0 but wit on other Issue. (Nullpointer Exception). But no Time to trace this Issue down at the moment.
> Let you know if I had news to that.
>
> Martin
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Romain Manni-Bucau [mailto:rmannibucau@gmail.com]
> Gesendet: Freitag, 22. August 2014 13:33
> An: users@tomee.apache.org
> Betreff: Re: Application stop working with by switching from TomEE 1.6.0 to 1.6.0.1
>
> If you have 5mn would be great to get your feedback on 1.7.0. I remember I did something about it but can't find back which version
> (1.7 or trunk).
>
>
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
>
>
> 2014-08-22 13:28 GMT+02:00 Berner Martin <Ma...@qualitasag.ch>:
>> Hi Romain
>> I had replaced the jar which solves the Problem. I had Multiple CATALINA_BASE with same CATALINA_HOME not any of the Application are affected so I don’t like to replace the jar at CATALINA_HOME. But I'll try to put it in lib of CATALINA_BASE for the Instances with affected Applications.
>>
>> I stumble over the Problem when I tried to switch from 1.6.0 to 1.6.0.2. Lot of debugging searching and pain later I realised, that it even don’t work on 1.6.0 1 and get the major hint in changelog (change of Tomcatversion 7.0.51 -> 7.0.53). Didn't try the 1.7.0 but it is based on Tomcat 7.0.53 too so maybe there is the same Problem.
>>
>> Best regards
>> Martin Berner
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Romain Manni-Bucau [mailto:rmannibucau@gmail.com]
>> Gesendet: Freitag, 22. August 2014 13:07
>> An: users@tomee.apache.org
>> Betreff: Re: Application stop working with by switching from TomEE
>> 1.6.0 to 1.6.0.1
>>
>> Hi
>>
>> IIRC you can replace this jar
>>
>> BTW did you really wanted to say 1.6.0.1? isn't it 1.6.0.2 or 1.7.0?
>>
>>
>> Romain Manni-Bucau
>> Twitter: @rmannibucau
>> Blog: http://rmannibucau.wordpress.com/
>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
>> Github: https://github.com/rmannibucau
>>
>>
>> 2014-08-22 11:37 GMT+02:00 Berner Martin <Ma...@qualitasag.ch>:
>>> Hi all
>>> I have a EL problem since new Versions of TomEE are based on Tomcat 7.0.53. Problem depends on a Fix in jasper-el.jar.
>>>
>>> When org.apache.el.parser.AstValue.getValue calls
>>> javax.el.BeanELResolver.invoke(ELContext context, Object base, Object
>>> method, Class<?>[] paramTypes, Object[] params)
>>>
>>> In Version before Tomcat 7.0.53 the Value paramTypes was null in my situation. With 7.0.53 the value is an Array with one null Entry.
>>> The invoke try to find an appropriate Method by looping over all Methods when paramTypes is null put now it isn't! So it works different and fails with a NoSuchMethodException.
>>>
>>> Is there anyone who has similar Problems or any Hints, Fixes, Workarounds?
>>>
>>> Any Help is appreciated.
>>>
>>> Best regards
>>> Martin Berner
AW: Application stop working with by switching from TomEE 1.6.0 to
1.6.0.1
Posted by Berner Martin <Ma...@qualitasag.ch>.
Hi Romain,
Application doesn't start under 1.7.0 because of a NullPointerException with a LazyRealm.
This is declaration in context.xml:
<Realm className="org.apache.tomee.catalina.realm.LazyRealm"
realmClass="ch.qual.base.app.realm.ContextDatabaseRealm"
cdi="true" />
And that’s the Logg by starting Application:
Schwerwiegend: A child container failed during start
java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/MilkSheepWeb]]
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:188)
at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:1123)
at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:816)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1575)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1565)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)
Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/MilkSheepWeb]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
... 6 more
Caused by: org.apache.catalina.LifecycleException: Failed to initialize component [org.apache.tomee.catalina.realm.LazyRealm@4946ed22]
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:106)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5373)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
... 6 more
Caused by: java.lang.NullPointerException
at org.apache.tomee.catalina.realm.LazyRealm.instance(LazyRealm.java:106)
at org.apache.tomee.catalina.realm.LazyRealm.initInternal(LazyRealm.java:130)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
... 9 more
Martin Berner
-----Ursprüngliche Nachricht-----
Von: Berner Martin [mailto:Martin.Berner@qualitasag.ch]
Gesendet: Freitag, 22. August 2014 13:51
An: 'users@tomee.apache.org'
Betreff: AW: Application stop working with by switching from TomEE 1.6.0 to 1.6.0.1
Hi Romain
get it to work by copying the jasper-el.jar from 1.6.0 to the lib of CATALINA_HOME (confound the Variables in last Explanation) and running with TomEE 1.6.0.2.
No success with 1.7.0 but wit on other Issue. (Nullpointer Exception). But no Time to trace this Issue down at the moment.
Let you know if I had news to that.
Martin
-----Ursprüngliche Nachricht-----
Von: Romain Manni-Bucau [mailto:rmannibucau@gmail.com]
Gesendet: Freitag, 22. August 2014 13:33
An: users@tomee.apache.org
Betreff: Re: Application stop working with by switching from TomEE 1.6.0 to 1.6.0.1
If you have 5mn would be great to get your feedback on 1.7.0. I remember I did something about it but can't find back which version
(1.7 or trunk).
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-08-22 13:28 GMT+02:00 Berner Martin <Ma...@qualitasag.ch>:
> Hi Romain
> I had replaced the jar which solves the Problem. I had Multiple CATALINA_BASE with same CATALINA_HOME not any of the Application are affected so I don’t like to replace the jar at CATALINA_HOME. But I'll try to put it in lib of CATALINA_BASE for the Instances with affected Applications.
>
> I stumble over the Problem when I tried to switch from 1.6.0 to 1.6.0.2. Lot of debugging searching and pain later I realised, that it even don’t work on 1.6.0 1 and get the major hint in changelog (change of Tomcatversion 7.0.51 -> 7.0.53). Didn't try the 1.7.0 but it is based on Tomcat 7.0.53 too so maybe there is the same Problem.
>
> Best regards
> Martin Berner
>
> -----Ursprüngliche Nachricht-----
> Von: Romain Manni-Bucau [mailto:rmannibucau@gmail.com]
> Gesendet: Freitag, 22. August 2014 13:07
> An: users@tomee.apache.org
> Betreff: Re: Application stop working with by switching from TomEE
> 1.6.0 to 1.6.0.1
>
> Hi
>
> IIRC you can replace this jar
>
> BTW did you really wanted to say 1.6.0.1? isn't it 1.6.0.2 or 1.7.0?
>
>
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
>
>
> 2014-08-22 11:37 GMT+02:00 Berner Martin <Ma...@qualitasag.ch>:
>> Hi all
>> I have a EL problem since new Versions of TomEE are based on Tomcat 7.0.53. Problem depends on a Fix in jasper-el.jar.
>>
>> When org.apache.el.parser.AstValue.getValue calls
>> javax.el.BeanELResolver.invoke(ELContext context, Object base, Object
>> method, Class<?>[] paramTypes, Object[] params)
>>
>> In Version before Tomcat 7.0.53 the Value paramTypes was null in my situation. With 7.0.53 the value is an Array with one null Entry.
>> The invoke try to find an appropriate Method by looping over all Methods when paramTypes is null put now it isn't! So it works different and fails with a NoSuchMethodException.
>>
>> Is there anyone who has similar Problems or any Hints, Fixes, Workarounds?
>>
>> Any Help is appreciated.
>>
>> Best regards
>> Martin Berner
AW: Application stop working with by switching from TomEE 1.6.0 to
1.6.0.1
Posted by Berner Martin <Ma...@qualitasag.ch>.
Hi Romain
get it to work by copying the jasper-el.jar from 1.6.0 to the lib of CATALINA_HOME (confound the Variables in last Explanation) and running with TomEE 1.6.0.2.
No success with 1.7.0 but wit on other Issue. (Nullpointer Exception). But no Time to trace this Issue down at the moment.
Let you know if I had news to that.
Martin
-----Ursprüngliche Nachricht-----
Von: Romain Manni-Bucau [mailto:rmannibucau@gmail.com]
Gesendet: Freitag, 22. August 2014 13:33
An: users@tomee.apache.org
Betreff: Re: Application stop working with by switching from TomEE 1.6.0 to 1.6.0.1
If you have 5mn would be great to get your feedback on 1.7.0. I remember I did something about it but can't find back which version
(1.7 or trunk).
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-08-22 13:28 GMT+02:00 Berner Martin <Ma...@qualitasag.ch>:
> Hi Romain
> I had replaced the jar which solves the Problem. I had Multiple CATALINA_BASE with same CATALINA_HOME not any of the Application are affected so I don’t like to replace the jar at CATALINA_HOME. But I'll try to put it in lib of CATALINA_BASE for the Instances with affected Applications.
>
> I stumble over the Problem when I tried to switch from 1.6.0 to 1.6.0.2. Lot of debugging searching and pain later I realised, that it even don’t work on 1.6.0 1 and get the major hint in changelog (change of Tomcatversion 7.0.51 -> 7.0.53). Didn't try the 1.7.0 but it is based on Tomcat 7.0.53 too so maybe there is the same Problem.
>
> Best regards
> Martin Berner
>
> -----Ursprüngliche Nachricht-----
> Von: Romain Manni-Bucau [mailto:rmannibucau@gmail.com]
> Gesendet: Freitag, 22. August 2014 13:07
> An: users@tomee.apache.org
> Betreff: Re: Application stop working with by switching from TomEE
> 1.6.0 to 1.6.0.1
>
> Hi
>
> IIRC you can replace this jar
>
> BTW did you really wanted to say 1.6.0.1? isn't it 1.6.0.2 or 1.7.0?
>
>
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
>
>
> 2014-08-22 11:37 GMT+02:00 Berner Martin <Ma...@qualitasag.ch>:
>> Hi all
>> I have a EL problem since new Versions of TomEE are based on Tomcat 7.0.53. Problem depends on a Fix in jasper-el.jar.
>>
>> When org.apache.el.parser.AstValue.getValue calls
>> javax.el.BeanELResolver.invoke(ELContext context, Object base, Object
>> method, Class<?>[] paramTypes, Object[] params)
>>
>> In Version before Tomcat 7.0.53 the Value paramTypes was null in my situation. With 7.0.53 the value is an Array with one null Entry.
>> The invoke try to find an appropriate Method by looping over all Methods when paramTypes is null put now it isn't! So it works different and fails with a NoSuchMethodException.
>>
>> Is there anyone who has similar Problems or any Hints, Fixes, Workarounds?
>>
>> Any Help is appreciated.
>>
>> Best regards
>> Martin Berner
Re: Application stop working with by switching from TomEE 1.6.0 to 1.6.0.1
Posted by Romain Manni-Bucau <rm...@gmail.com>.
If you have 5mn would be great to get your feedback on 1.7.0. I
remember I did something about it but can't find back which version
(1.7 or trunk).
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-08-22 13:28 GMT+02:00 Berner Martin <Ma...@qualitasag.ch>:
> Hi Romain
> I had replaced the jar which solves the Problem. I had Multiple CATALINA_BASE with same CATALINA_HOME not any of the Application are affected so I don’t like to replace the jar at CATALINA_HOME. But I'll try to put it in lib of CATALINA_BASE for the Instances with affected Applications.
>
> I stumble over the Problem when I tried to switch from 1.6.0 to 1.6.0.2. Lot of debugging searching and pain later I realised, that it even don’t work on 1.6.0 1 and get the major hint in changelog (change of Tomcatversion 7.0.51 -> 7.0.53). Didn't try the 1.7.0 but it is based on Tomcat 7.0.53 too so maybe there is the same Problem.
>
> Best regards
> Martin Berner
>
> -----Ursprüngliche Nachricht-----
> Von: Romain Manni-Bucau [mailto:rmannibucau@gmail.com]
> Gesendet: Freitag, 22. August 2014 13:07
> An: users@tomee.apache.org
> Betreff: Re: Application stop working with by switching from TomEE 1.6.0 to 1.6.0.1
>
> Hi
>
> IIRC you can replace this jar
>
> BTW did you really wanted to say 1.6.0.1? isn't it 1.6.0.2 or 1.7.0?
>
>
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
>
>
> 2014-08-22 11:37 GMT+02:00 Berner Martin <Ma...@qualitasag.ch>:
>> Hi all
>> I have a EL problem since new Versions of TomEE are based on Tomcat 7.0.53. Problem depends on a Fix in jasper-el.jar.
>>
>> When org.apache.el.parser.AstValue.getValue calls javax.el.BeanELResolver.invoke(ELContext context, Object base, Object method, Class<?>[] paramTypes, Object[] params)
>>
>> In Version before Tomcat 7.0.53 the Value paramTypes was null in my situation. With 7.0.53 the value is an Array with one null Entry.
>> The invoke try to find an appropriate Method by looping over all Methods when paramTypes is null put now it isn't! So it works different and fails with a NoSuchMethodException.
>>
>> Is there anyone who has similar Problems or any Hints, Fixes, Workarounds?
>>
>> Any Help is appreciated.
>>
>> Best regards
>> Martin Berner
AW: Application stop working with by switching from TomEE 1.6.0 to
1.6.0.1
Posted by Berner Martin <Ma...@qualitasag.ch>.
Hi Romain
I had replaced the jar which solves the Problem. I had Multiple CATALINA_BASE with same CATALINA_HOME not any of the Application are affected so I don’t like to replace the jar at CATALINA_HOME. But I'll try to put it in lib of CATALINA_BASE for the Instances with affected Applications.
I stumble over the Problem when I tried to switch from 1.6.0 to 1.6.0.2. Lot of debugging searching and pain later I realised, that it even don’t work on 1.6.0 1 and get the major hint in changelog (change of Tomcatversion 7.0.51 -> 7.0.53). Didn't try the 1.7.0 but it is based on Tomcat 7.0.53 too so maybe there is the same Problem.
Best regards
Martin Berner
-----Ursprüngliche Nachricht-----
Von: Romain Manni-Bucau [mailto:rmannibucau@gmail.com]
Gesendet: Freitag, 22. August 2014 13:07
An: users@tomee.apache.org
Betreff: Re: Application stop working with by switching from TomEE 1.6.0 to 1.6.0.1
Hi
IIRC you can replace this jar
BTW did you really wanted to say 1.6.0.1? isn't it 1.6.0.2 or 1.7.0?
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-08-22 11:37 GMT+02:00 Berner Martin <Ma...@qualitasag.ch>:
> Hi all
> I have a EL problem since new Versions of TomEE are based on Tomcat 7.0.53. Problem depends on a Fix in jasper-el.jar.
>
> When org.apache.el.parser.AstValue.getValue calls javax.el.BeanELResolver.invoke(ELContext context, Object base, Object method, Class<?>[] paramTypes, Object[] params)
>
> In Version before Tomcat 7.0.53 the Value paramTypes was null in my situation. With 7.0.53 the value is an Array with one null Entry.
> The invoke try to find an appropriate Method by looping over all Methods when paramTypes is null put now it isn't! So it works different and fails with a NoSuchMethodException.
>
> Is there anyone who has similar Problems or any Hints, Fixes, Workarounds?
>
> Any Help is appreciated.
>
> Best regards
> Martin Berner
Re: Application stop working with by switching from TomEE 1.6.0 to 1.6.0.1
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hi
IIRC you can replace this jar
BTW did you really wanted to say 1.6.0.1? isn't it 1.6.0.2 or 1.7.0?
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-08-22 11:37 GMT+02:00 Berner Martin <Ma...@qualitasag.ch>:
> Hi all
> I have a EL problem since new Versions of TomEE are based on Tomcat 7.0.53. Problem depends on a Fix in jasper-el.jar.
>
> When org.apache.el.parser.AstValue.getValue calls javax.el.BeanELResolver.invoke(ELContext context, Object base, Object method, Class<?>[] paramTypes, Object[] params)
>
> In Version before Tomcat 7.0.53 the Value paramTypes was null in my situation. With 7.0.53 the value is an Array with one null Entry.
> The invoke try to find an appropriate Method by looping over all Methods when paramTypes is null put now it isn't! So it works different and fails with a NoSuchMethodException.
>
> Is there anyone who has similar Problems or any Hints, Fixes, Workarounds?
>
> Any Help is appreciated.
>
> Best regards
> Martin Berner