You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomee.apache.org by kvrohit <kv...@gmail.com> on 2015/04/10 07:49:29 UTC
Does TomEE 1.7.1 support JSF 1.1?
Greetings,
I am trying to deploy a legacy JSF 1.1 application on TomEE, so far I am not
able to get it working. After trying several options, I am of the opinion
that doing this is not possible on TomEE. Is this true?
If not, then could you point to some documentation on how to get this
working?
TomEE version used: Plume
Thanks!
--
View this message in context: http://tomee-openejb.979440.n4.nabble.com/Does-TomEE-1-7-1-support-JSF-1-1-tp4674353.html
Sent from the TomEE Users mailing list archive at Nabble.com.
Re: Does TomEE 1.7.1 support JSF 1.1?
Posted by kvrohit <kv...@gmail.com>.
Cool. Will check once the snapshot is available...
--
View this message in context: http://tomee-openejb.979440.n4.nabble.com/Does-TomEE-1-7-1-support-JSF-1-1-tp4674353p4674366.html
Sent from the TomEE Users mailing list archive at Nabble.com.
Re: Does TomEE 1.7.1 support JSF 1.1?
Posted by Mark Struberg <st...@yahoo.de>.
OpenWebBeans is built in a very modular fashion. We add integration features by simply dropping the plugin into the classpath. The webbeans-jsf* module adds support for 2 features:
1.) CDI @ConversationScoped support for JSF
2.) CDI EL support for JSF.
Out of the box we have plugins to support JSF-2.0++ and JSF-1.2. We do not support JSF-1.1 (was way too old in 2009 already).
Which parts do you need for your JSF application? Do you need CDI @ConversationScoped integration?
If you only need EL integration then you probably can add the WebBeansELResolver in your faces-application.xml and remove webbeans-jsf* completely?
LieGrue,
strub
> Am 22.04.2015 um 03:12 schrieb kvrohit <kv...@gmail.com>:
>
> Hi Romain,
>
> Thanks for the workaround, I tried both the options; but they don't work as
> expected. The application deploys but does not render correctly; one sample
> scenario I tried was h:outputLink, the markup generated was in correct.
>
> Is there any chance that the fix will be added to support JSF 1.1?
>
> Thanks,
> Rohit
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.n4.nabble.com/Does-TomEE-1-7-1-support-JSF-1-1-tp4674353p4674559.html
> Sent from the TomEE Users mailing list archive at Nabble.com.
Re: Does TomEE 1.7.1 support JSF 1.1?
Posted by kvrohit <kv...@gmail.com>.
Hi Romain,
Thanks for the workaround, I tried both the options; but they don't work as
expected. The application deploys but does not render correctly; one sample
scenario I tried was h:outputLink, the markup generated was in correct.
Is there any chance that the fix will be added to support JSF 1.1?
Thanks,
Rohit
--
View this message in context: http://tomee-openejb.979440.n4.nabble.com/Does-TomEE-1-7-1-support-JSF-1-1-tp4674353p4674559.html
Sent from the TomEE Users mailing list archive at Nabble.com.
Re: Does TomEE 1.7.1 support JSF 1.1?
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hi
Used openwebbeans-jsf12-1.5.0-SNAPSHOT.jar but should be pretty much the
same as 1.2.7 version (but didnt check).
You are surely right the fix was mainly for 1.2 jsf apps, that said I can
propose you to test 2 things:
1- if you app is just a legacy one (hope so ;)) then remove from tomee/lib
openwebbeans-jsf*
2- if not you'll need to repackage openejb-jsf12 to remove the view-handler
from faces-config.xml
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com>
2015-04-17 10:00 GMT+02:00 kvrohit <kv...@gmail.com>:
> Hi Romain,
>
> I downloaded a 2.0.0 snapshot from
>
> https://repository.apache.org/content/groups/snapshots/org/apache/openejb/apache-tomee/2.0.0-SNAPSHOT/
> (Apr 16 build) today to test the fix out... Ran some tests:
>
> 1. Created JSF1.1 and JSF1.2 sample apps
> 2. Replaced the openwebbeans-jsf-1.5.0-SNAPSHOT.jar with
> openwebbeans-jsf12-1.2.7.jar
> 3. Ran the server
>
> Results:
> *1. JSF1.1 app does not work, fails with the following error:*
>
> 17-Apr-2015 12:41:44.488 SEVERE [http-nio-8080-exec-4]
> org.apache.catalina.core.StandardContext.listenerStart Exception sending
> context initialized event to listener instance of class
> com.sun.faces.config.ConfigureListener
> java.lang.VerifyError: JVMVRFY013 class loading constraint violated;
> class=org/apache/webbeans/jsf12/ConversationAwareViewHandler,
> method=getWrapped()Ljavax/faces/application/ViewHandler;, pc=0
> at java.lang.J9VMInternals.verifyImpl(Native Method)
> at java.lang.J9VMInternals.verify(J9VMInternals.java:90)
> at java.lang.J9VMInternals.initialize(J9VMInternals.java:167)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
>
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:80)
> at
>
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:57)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:539)
> at com.sun.faces.util.Util.createInstance(Util.java:1160)
> at
>
> com.sun.faces.config.ConfigureListener.configure(ConfigureListener.java:539)
> at
>
> com.sun.faces.config.ConfigureListener.configure(ConfigureListener.java:402)
> at
>
> com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:332)
> at
>
> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4728)
> at
>
> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5166)
> at
> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
> at
> org.apache.catalina.manager.ManagerServlet.start(ManagerServlet.java:1293)
> at
>
> org.apache.catalina.manager.HTMLManagerServlet.start(HTMLManagerServlet.java:673)
> at
>
> org.apache.catalina.manager.HTMLManagerServlet.doPost(HTMLManagerServlet.java:221)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:648)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
> at
>
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:291)
> at
>
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at
>
> org.apache.catalina.filters.CsrfPreventionFilter.doFilter(CsrfPreventionFilter.java:213)
> at
>
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
> at
>
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at
> org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
> at
>
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
> at
>
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at
>
> org.apache.catalina.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:108)
> at
>
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
> at
>
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at
>
> org.apache.openejb.server.httpd.WebBeansFilter.doFilter(WebBeansFilter.java:51)
> at
>
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
> at
>
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at
>
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:219)
> at
>
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:106)
> at
> org.apache.tomee.catalina.OpenEJBValve.invoke(OpenEJBValve.java:44)
> at
>
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:614)
> at
>
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:142)
> at
>
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)
> at
>
> org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:610)
> at
>
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:518)
> at
>
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1091)
> at
>
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:668)
> at
>
> org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:223)
> at
>
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1517)
> at
>
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1474)
> at
>
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1121)
> at
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:614)
> at
>
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
> at java.lang.Thread.run(Thread.java:769)
>
> *2. JSF1.2 application works!*
>
> So my question is, does the fix address the 1.1 issue? If so, where can I
> find the correct snapshot? Or do I have to build tomee from source?
>
> I see that you were able to run the sample application that I had posted.
> However, I cannot get it to run in my setup. Let me know your comments.
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/Does-TomEE-1-7-1-support-JSF-1-1-tp4674353p4674459.html
> Sent from the TomEE Users mailing list archive at Nabble.com.
>
Re: Does TomEE 1.7.1 support JSF 1.1?
Posted by kvrohit <kv...@gmail.com>.
Hi Romain,
I downloaded a 2.0.0 snapshot from
https://repository.apache.org/content/groups/snapshots/org/apache/openejb/apache-tomee/2.0.0-SNAPSHOT/
(Apr 16 build) today to test the fix out... Ran some tests:
1. Created JSF1.1 and JSF1.2 sample apps
2. Replaced the openwebbeans-jsf-1.5.0-SNAPSHOT.jar with
openwebbeans-jsf12-1.2.7.jar
3. Ran the server
Results:
*1. JSF1.1 app does not work, fails with the following error:*
17-Apr-2015 12:41:44.488 SEVERE [http-nio-8080-exec-4]
org.apache.catalina.core.StandardContext.listenerStart Exception sending
context initialized event to listener instance of class
com.sun.faces.config.ConfigureListener
java.lang.VerifyError: JVMVRFY013 class loading constraint violated;
class=org/apache/webbeans/jsf12/ConversationAwareViewHandler,
method=getWrapped()Ljavax/faces/application/ViewHandler;, pc=0
at java.lang.J9VMInternals.verifyImpl(Native Method)
at java.lang.J9VMInternals.verify(J9VMInternals.java:90)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:167)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:80)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:57)
at java.lang.reflect.Constructor.newInstance(Constructor.java:539)
at com.sun.faces.util.Util.createInstance(Util.java:1160)
at
com.sun.faces.config.ConfigureListener.configure(ConfigureListener.java:539)
at
com.sun.faces.config.ConfigureListener.configure(ConfigureListener.java:402)
at
com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:332)
at
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4728)
at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5166)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at
org.apache.catalina.manager.ManagerServlet.start(ManagerServlet.java:1293)
at
org.apache.catalina.manager.HTMLManagerServlet.start(HTMLManagerServlet.java:673)
at
org.apache.catalina.manager.HTMLManagerServlet.doPost(HTMLManagerServlet.java:221)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:648)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:291)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.filters.CsrfPreventionFilter.doFilter(CsrfPreventionFilter.java:213)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:108)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.openejb.server.httpd.WebBeansFilter.doFilter(WebBeansFilter.java:51)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:219)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:106)
at org.apache.tomee.catalina.OpenEJBValve.invoke(OpenEJBValve.java:44)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:614)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:142)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)
at
org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:610)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:518)
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1091)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:668)
at
org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:223)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1517)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1474)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1121)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:614)
at
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:769)
*2. JSF1.2 application works!*
So my question is, does the fix address the 1.1 issue? If so, where can I
find the correct snapshot? Or do I have to build tomee from source?
I see that you were able to run the sample application that I had posted.
However, I cannot get it to run in my setup. Let me know your comments.
--
View this message in context: http://tomee-openejb.979440.n4.nabble.com/Does-TomEE-1-7-1-support-JSF-1-1-tp4674353p4674459.html
Sent from the TomEE Users mailing list archive at Nabble.com.
Re: Does TomEE 1.7.1 support JSF 1.1?
Posted by Romain Manni-Bucau <rm...@gmail.com>.
PS: your app now runs on tomee 2 (snapshot is not yet deployed on
https://repository.apache.org/content/groups/snapshots/org/apache/openejb/apache-tomee/
but
you can build it yourself from sources if you want)
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com>
2015-04-10 16:25 GMT+02:00 Romain Manni-Bucau <rm...@gmail.com>:
>
> 2015-04-10 16:09 GMT+02:00 kvrohit <kv...@gmail.com>:
>
>> Hi Romain,
>>
>> Thanks for the quick response! I see that a defect has been opened for
>> this.
>> I took a look at it and it says Fixed in 2.0.0-Milestone-1. So, have a few
>> follow up questions:
>>
>> 1. Can I use 2.0.0 to deploy my app? If so, where can I download it?
>>
>
> Not yet, few other things are blocking - not sure anymore it is 2.x
> specific or in 1.7 as well
>
>
>> 2. What is the general availability for 2.0.0?
>>
>
> Soon hopefully - 1st quarter
>
>
>> 3. Will this fix be back ported to 1.7.1?
>>
>
> Can be
>
> Note: you still need to replace openwebbeans-jsf by openwebbeans-jsf12 in
> tomee/lib cause of changes in JSF API
>
>
>>
>> - Rohit
>>
>>
>>
>> --
>> View this message in context:
>> http://tomee-openejb.979440.n4.nabble.com/Does-TomEE-1-7-1-support-JSF-1-1-tp4674353p4674363.html
>> Sent from the TomEE Users mailing list archive at Nabble.com.
>>
>
>
Re: Does TomEE 1.7.1 support JSF 1.1?
Posted by Mark Struberg <st...@yahoo.de>.
I think it should also work in 1.7.1.
This is actually not a bug but basically some modularity feature you get from OpenWebBeans.
Basically CDI is JavaEE6. But in OpenWebBeans we still support a lot of older integration scenarios as well. And even pure Java SE. OWB is built around a ‚core‘ which has only 450k and supports SE + interceptors, decorators, etc (in comparision to our size even Guice with it’s 3.5MB looks fat). All other EE integration features are added as ‚OpenWebBeans-plugins‘.
As TomEE-1.7.x targets EE6 and TomEE-2.0.x even EE7 it by default packages the JSF2 support module. The difference between JSF-1.2 and JSF-2 is mainly the handling of the ‚Application‘ interface [1]. Up to JSF-1.2 you had to implement a custom Application (we need that to attach our own CDI EL-Resolver) for each JSF version. And the Application interface got changed a lot with each JSF version.
To not having to provide an own version of JSF integration code over and over again the JSF EG decided to introduce an Abstract ApplicationWrapper base class [1]. This is what we use by default in our webbeans-jsf (that is JSF2) module. The webbeans-jsf12 module cannot use this new abstract class though. And that is the reason why you need to switch those 2 jars if you like to run with a JSF-1.2 container like Mojarra-1.2.
LieGrue,
strub
PS: I always prefer explaining those kind of things to developers instead of simply telling them what to do in a blackbox kind of way. We are all cooking with water still - although our water is pretty damn hot sometimes ;)
[1] http://docs.oracle.com/javaee/6/api/javax/faces/application/Application.html
[2] http://docs.oracle.com/javaee/6/api/javax/faces/application/ApplicationWrapper.html
> Am 10.04.2015 um 16:25 schrieb Romain Manni-Bucau <rm...@gmail.com>:
>
> 2015-04-10 16:09 GMT+02:00 kvrohit <kv...@gmail.com>:
>
>> Hi Romain,
>>
>> Thanks for the quick response! I see that a defect has been opened for
>> this.
>> I took a look at it and it says Fixed in 2.0.0-Milestone-1. So, have a few
>> follow up questions:
>>
>> 1. Can I use 2.0.0 to deploy my app? If so, where can I download it?
>>
>
> Not yet, few other things are blocking - not sure anymore it is 2.x
> specific or in 1.7 as well
>
>
>> 2. What is the general availability for 2.0.0?
>>
>
> Soon hopefully - 1st quarter
>
>
>> 3. Will this fix be back ported to 1.7.1?
>>
>
> Can be
>
> Note: you still need to replace openwebbeans-jsf by openwebbeans-jsf12 in
> tomee/lib cause of changes in JSF API
>
>
>>
>> - Rohit
>>
>>
>>
>> --
>> View this message in context:
>> http://tomee-openejb.979440.n4.nabble.com/Does-TomEE-1-7-1-support-JSF-1-1-tp4674353p4674363.html
>> Sent from the TomEE Users mailing list archive at Nabble.com.
>>
Re: Does TomEE 1.7.1 support JSF 1.1?
Posted by Romain Manni-Bucau <rm...@gmail.com>.
2015-04-10 16:09 GMT+02:00 kvrohit <kv...@gmail.com>:
> Hi Romain,
>
> Thanks for the quick response! I see that a defect has been opened for
> this.
> I took a look at it and it says Fixed in 2.0.0-Milestone-1. So, have a few
> follow up questions:
>
> 1. Can I use 2.0.0 to deploy my app? If so, where can I download it?
>
Not yet, few other things are blocking - not sure anymore it is 2.x
specific or in 1.7 as well
> 2. What is the general availability for 2.0.0?
>
Soon hopefully - 1st quarter
> 3. Will this fix be back ported to 1.7.1?
>
Can be
Note: you still need to replace openwebbeans-jsf by openwebbeans-jsf12 in
tomee/lib cause of changes in JSF API
>
> - Rohit
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/Does-TomEE-1-7-1-support-JSF-1-1-tp4674353p4674363.html
> Sent from the TomEE Users mailing list archive at Nabble.com.
>
Re: Does TomEE 1.7.1 support JSF 1.1?
Posted by kvrohit <kv...@gmail.com>.
Hi Romain,
Thanks for the quick response! I see that a defect has been opened for this.
I took a look at it and it says Fixed in 2.0.0-Milestone-1. So, have a few
follow up questions:
1. Can I use 2.0.0 to deploy my app? If so, where can I download it?
2. What is the general availability for 2.0.0?
3. Will this fix be back ported to 1.7.1?
- Rohit
--
View this message in context: http://tomee-openejb.979440.n4.nabble.com/Does-TomEE-1-7-1-support-JSF-1-1-tp4674353p4674363.html
Sent from the TomEE Users mailing list archive at Nabble.com.
Re: Does TomEE 1.7.1 support JSF 1.1?
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hi
surely linked to https://issues.apache.org/jira/browse/TOMEE-1546
can still have few issues later but you are right this is not easy to
workaround
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com>
2015-04-10 14:05 GMT+02:00 kvrohit <kv...@gmail.com>:
> I wrote a simple JSF1.1 app to reproduce the issue. Here is the output from
> the logs:
>
> Apr 10, 2015 5:06:37 PM org.apache.catalina.core.StandardWrapperValve
> invoke
> SEVERE: Servlet.service() for servlet [Faces Servlet] in context with path
> [/jsf1-app] threw exception
> java.lang.UnsupportedOperationException
> at
>
> javax.faces.application.Application.getResourceHandler(Application.java:862)
> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:185)
> at
>
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
> at
>
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at
> org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
> at
>
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
> at
>
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at
>
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
> at
>
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
> at org.apache.tomee.catalina.OpenEJBValve.invoke(OpenEJBValve.java:44)
> at
>
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501)
> at
>
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
> at
>
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
> at
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
> at
>
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
> at
>
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1070)
> at
>
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:611)
> at
>
> org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:314)
> at
>
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1121)
> at
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:614)
> at
>
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
> at java.lang.Thread.run(Thread.java:769)
>
> Attaching the sample app so that you can deploy and see the same.
>
>
> On Fri, 10 Apr 2015 at 12:25 Romain Manni-Bucau [via TomEE & OpenEJB] <
> ml-node+s979440n4674358h48@n4.nabble.com> wrote:
>
> > well remplacing 2.x jars by 1.x shouldnt work well but using 2.x impl
> > shouldnt prevent 1.x usage.
> >
> >
> > Once again if you want help please give us your error.
> >
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> | Blog
> > <http://rmannibucau.wordpress.com> | Github <
> > https://github.com/rmannibucau> |
> > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> > <http://www.tomitribe.com>
> >
> > 2015-04-10 8:14 GMT+02:00 kvrohit <[hidden email]
> > <http:///user/SendEmail.jtp?type=node&node=4674358&i=0>>:
> >
> > > My app is using mojarra instead of myfaces.
> > >
> > > I am not able to get the 1.1 jars loaded, by default it uses the 2.x
> > > implementation of JSF. I tried the following:
> > > 1. Remove the javax.faces-2.1.29.jar from TomEE/lib folder
> > > 2. Put in the JSF 1.1 jars (jsf-api and jsf-impl) in the lib folder and
> > > start server
> > >
> > > When I do this, none of the built in apps show up. I figured that they
> > > require the default implementations so removing the 2.x jar from lib
> > folder
> > > is not a good way to go.
> > >
> > > Now, I came across this setting openejb.classloader.forced-load that
> can
> > be
> > > used tell the app server to use my libs (in /WEB-INF/lib), however, I
> > could
> > > not get it to work. Is this setting required?
> > >
> > > I will try removing all the jsf jars from the TomEE/lib folder while
> > just
> > > using the ones bundled in the WebApp and let you know how it goes...
> > >
> > >
> > >
> > > --
> > > View this message in context:
> > >
> >
> http://tomee-openejb.979440.n4.nabble.com/Does-TomEE-1-7-1-support-JSF-1-1-tp4674353p4674357.html
> >
> > > Sent from the TomEE Users mailing list archive at Nabble.com.
> > >
> > If you reply to this email, your message will be added to the discussion
> > below:
> >
> >
> http://tomee-openejb.979440.n4.nabble.com/Does-TomEE-1-7-1-support-JSF-1-1-tp4674353p4674358.html
> > To unsubscribe from Does TomEE 1.7.1 support JSF 1.1?, click here
> > <
> http://tomee-openejb.979440.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4674353&code=a3Zyb2hpdEBnbWFpbC5jb218NDY3NDM1M3wtMjExNDUzNDcy
> >
> > .
> > NAML
> > <
> http://tomee-openejb.979440.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
> >
> >
>
>
> jsf1-app.zip (1M) <
> http://tomee-openejb.979440.n4.nabble.com/attachment/4674361/0/jsf1-app.zip
> >
>
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/Does-TomEE-1-7-1-support-JSF-1-1-tp4674353p4674361.html
> Sent from the TomEE Users mailing list archive at Nabble.com.
>
Re: Does TomEE 1.7.1 support JSF 1.1?
Posted by kvrohit <kv...@gmail.com>.
I wrote a simple JSF1.1 app to reproduce the issue. Here is the output from
the logs:
Apr 10, 2015 5:06:37 PM org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet [Faces Servlet] in context with path
[/jsf1-app] threw exception
java.lang.UnsupportedOperationException
at
javax.faces.application.Application.getResourceHandler(Application.java:862)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:185)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
at org.apache.tomee.catalina.OpenEJBValve.invoke(OpenEJBValve.java:44)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1070)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:611)
at
org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:314)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1121)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:614)
at
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:769)
Attaching the sample app so that you can deploy and see the same.
On Fri, 10 Apr 2015 at 12:25 Romain Manni-Bucau [via TomEE & OpenEJB] <
ml-node+s979440n4674358h48@n4.nabble.com> wrote:
> well remplacing 2.x jars by 1.x shouldnt work well but using 2.x impl
> shouldnt prevent 1.x usage.
>
>
> Once again if you want help please give us your error.
>
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> | Blog
> <http://rmannibucau.wordpress.com> | Github <
> https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> <http://www.tomitribe.com>
>
> 2015-04-10 8:14 GMT+02:00 kvrohit <[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=4674358&i=0>>:
>
> > My app is using mojarra instead of myfaces.
> >
> > I am not able to get the 1.1 jars loaded, by default it uses the 2.x
> > implementation of JSF. I tried the following:
> > 1. Remove the javax.faces-2.1.29.jar from TomEE/lib folder
> > 2. Put in the JSF 1.1 jars (jsf-api and jsf-impl) in the lib folder and
> > start server
> >
> > When I do this, none of the built in apps show up. I figured that they
> > require the default implementations so removing the 2.x jar from lib
> folder
> > is not a good way to go.
> >
> > Now, I came across this setting openejb.classloader.forced-load that can
> be
> > used tell the app server to use my libs (in /WEB-INF/lib), however, I
> could
> > not get it to work. Is this setting required?
> >
> > I will try removing all the jsf jars from the TomEE/lib folder while
> just
> > using the ones bundled in the WebApp and let you know how it goes...
> >
> >
> >
> > --
> > View this message in context:
> >
> http://tomee-openejb.979440.n4.nabble.com/Does-TomEE-1-7-1-support-JSF-1-1-tp4674353p4674357.html
>
> > Sent from the TomEE Users mailing list archive at Nabble.com.
> >
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://tomee-openejb.979440.n4.nabble.com/Does-TomEE-1-7-1-support-JSF-1-1-tp4674353p4674358.html
> To unsubscribe from Does TomEE 1.7.1 support JSF 1.1?, click here
> <http://tomee-openejb.979440.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4674353&code=a3Zyb2hpdEBnbWFpbC5jb218NDY3NDM1M3wtMjExNDUzNDcy>
> .
> NAML
> <http://tomee-openejb.979440.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
jsf1-app.zip (1M) <http://tomee-openejb.979440.n4.nabble.com/attachment/4674361/0/jsf1-app.zip>
--
View this message in context: http://tomee-openejb.979440.n4.nabble.com/Does-TomEE-1-7-1-support-JSF-1-1-tp4674353p4674361.html
Sent from the TomEE Users mailing list archive at Nabble.com.
Re: Does TomEE 1.7.1 support JSF 1.1?
Posted by kvrohit <kv...@gmail.com>.
I wrote a simple JSF1.1 app to reproduce the issue. Here is the output from
the logs:
Apr 10, 2015 5:06:37 PM org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet [Faces Servlet] in context with path
[/jsf1-app] threw exception
java.lang.UnsupportedOperationException
at
javax.faces.application.Application.getResourceHandler(Application.java:862)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:185)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
at org.apache.tomee.catalina.OpenEJBValve.invoke(OpenEJBValve.java:44)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1070)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:611)
at
org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:314)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1121)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:614)
at
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:769)
Attaching the sample app...
jsf1-app.zip
<http://tomee-openejb.979440.n4.nabble.com/file/n4674360/jsf1-app.zip>
--
View this message in context: http://tomee-openejb.979440.n4.nabble.com/Does-TomEE-1-7-1-support-JSF-1-1-tp4674353p4674360.html
Sent from the TomEE Users mailing list archive at Nabble.com.
Re: Does TomEE 1.7.1 support JSF 1.1?
Posted by Romain Manni-Bucau <rm...@gmail.com>.
well remplacing 2.x jars by 1.x shouldnt work well but using 2.x impl
shouldnt prevent 1.x usage.
Once again if you want help please give us your error.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com>
2015-04-10 8:14 GMT+02:00 kvrohit <kv...@gmail.com>:
> My app is using mojarra instead of myfaces.
>
> I am not able to get the 1.1 jars loaded, by default it uses the 2.x
> implementation of JSF. I tried the following:
> 1. Remove the javax.faces-2.1.29.jar from TomEE/lib folder
> 2. Put in the JSF 1.1 jars (jsf-api and jsf-impl) in the lib folder and
> start server
>
> When I do this, none of the built in apps show up. I figured that they
> require the default implementations so removing the 2.x jar from lib folder
> is not a good way to go.
>
> Now, I came across this setting openejb.classloader.forced-load that can be
> used tell the app server to use my libs (in /WEB-INF/lib), however, I could
> not get it to work. Is this setting required?
>
> I will try removing all the jsf jars from the TomEE/lib folder while just
> using the ones bundled in the WebApp and let you know how it goes...
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/Does-TomEE-1-7-1-support-JSF-1-1-tp4674353p4674357.html
> Sent from the TomEE Users mailing list archive at Nabble.com.
>
Re: Does TomEE 1.7.1 support JSF 1.1?
Posted by kvrohit <kv...@gmail.com>.
My app is using mojarra instead of myfaces.
I am not able to get the 1.1 jars loaded, by default it uses the 2.x
implementation of JSF. I tried the following:
1. Remove the javax.faces-2.1.29.jar from TomEE/lib folder
2. Put in the JSF 1.1 jars (jsf-api and jsf-impl) in the lib folder and
start server
When I do this, none of the built in apps show up. I figured that they
require the default implementations so removing the 2.x jar from lib folder
is not a good way to go.
Now, I came across this setting openejb.classloader.forced-load that can be
used tell the app server to use my libs (in /WEB-INF/lib), however, I could
not get it to work. Is this setting required?
I will try removing all the jsf jars from the TomEE/lib folder while just
using the ones bundled in the WebApp and let you know how it goes...
--
View this message in context: http://tomee-openejb.979440.n4.nabble.com/Does-TomEE-1-7-1-support-JSF-1-1-tp4674353p4674357.html
Sent from the TomEE Users mailing list archive at Nabble.com.
Re: Does TomEE 1.7.1 support JSF 1.1?
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hi
I dont see why it shouldnt without anything particular. Do you have a
stacktrace to share?
Le 10 avr. 2015 08:02, "kvrohit" <kv...@gmail.com> a écrit :
> Greetings,
>
> I am trying to deploy a legacy JSF 1.1 application on TomEE, so far I am
> not
> able to get it working. After trying several options, I am of the opinion
> that doing this is not possible on TomEE. Is this true?
>
> If not, then could you point to some documentation on how to get this
> working?
>
> TomEE version used: Plume
>
> Thanks!
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/Does-TomEE-1-7-1-support-JSF-1-1-tp4674353.html
> Sent from the TomEE Users mailing list archive at Nabble.com.
>
Re: Does TomEE 1.7.1 support JSF 1.1?
Posted by Romain Manni-Bucau <rm...@gmail.com>.
s/myfaces/mojarra/ i guess
Le 10 avr. 2015 08:19, "Andy Gumbrecht" <ag...@tomitribe.com> a écrit :
> Where does this legacy application currently run (what was the previous
> runtime / application server)?
>
> Anyway, you will need delete/remove the shipped myfaces-*.jars from the
> [TomEE]/lib directory and then include the old myfaces jars in your webapp.
>
> If you have multiple apps with odd myfaces versions then you will need to
> do this for all your apps.
>
> Andy.
>
> On 10 April 2015 at 07:49, kvrohit <kv...@gmail.com> wrote:
>
> > Greetings,
> >
> > I am trying to deploy a legacy JSF 1.1 application on TomEE, so far I am
> > not
> > able to get it working. After trying several options, I am of the opinion
> > that doing this is not possible on TomEE. Is this true?
> >
> > If not, then could you point to some documentation on how to get this
> > working?
> >
> > TomEE version used: Plume
> >
> > Thanks!
> >
> >
> >
> > --
> > View this message in context:
> >
> http://tomee-openejb.979440.n4.nabble.com/Does-TomEE-1-7-1-support-JSF-1-1-tp4674353.html
> > Sent from the TomEE Users mailing list archive at Nabble.com.
> >
>
Re: Does TomEE 1.7.1 support JSF 1.1?
Posted by Andy Gumbrecht <ag...@tomitribe.com>.
Where does this legacy application currently run (what was the previous
runtime / application server)?
Anyway, you will need delete/remove the shipped myfaces-*.jars from the
[TomEE]/lib directory and then include the old myfaces jars in your webapp.
If you have multiple apps with odd myfaces versions then you will need to
do this for all your apps.
Andy.
On 10 April 2015 at 07:49, kvrohit <kv...@gmail.com> wrote:
> Greetings,
>
> I am trying to deploy a legacy JSF 1.1 application on TomEE, so far I am
> not
> able to get it working. After trying several options, I am of the opinion
> that doing this is not possible on TomEE. Is this true?
>
> If not, then could you point to some documentation on how to get this
> working?
>
> TomEE version used: Plume
>
> Thanks!
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/Does-TomEE-1-7-1-support-JSF-1-1-tp4674353.html
> Sent from the TomEE Users mailing list archive at Nabble.com.
>