Re: MyFaces 1.2 + Tomahawk Kickstart was: Re: Myfaces 1.2.0 setup issues (again)
Martin Marinschek schrieb: So the outcome is that generally it works? What was the difference in the setup then? regards, Martin I have not looked to deeply into it yet - sleep before midnight makes sense ;-) , sorry, I was glad that it finally works. I assume it was/is a missing jar or an old version of a dependency. The main problem I still see is the dependency into commons-el which might cause sideeffects besides that nothing seems out of order for now.
Re: MyFaces 1.2 + Tomahawk Kickstart was: Re: Myfaces 1.2.0 setup issues (again)
Great work Werner.A true added value. This is smth useful we can all start from. -Wolf On 7/23/07, Werner Punz [EMAIL PROTECTED] wrote: Matthias Wessendorf schrieb: release often, release early ... :-) Ok guys I am dropping the tomahawk builds and the blank application as well as a working myfaces 1.2 sandbox war into http://people.apache.org/~werpu/ as we speak, first of all there is a slight build error, once extracted you safely can remove the jstl-1.1.jar from the WEB-INF/lib the wars should work out of the box on a tomcat 6 install with a jdk5+ most tomahawk components seem to work, the same goes for the sandbox, 3-4 fail on tomahawk, and the same on the sandbox for various reasons (most of them are slight programming errors, or misuse of the 1.1 spec to achieve a certain functionality) Note, all this wont work with jdk 1.4 or a non JEE5 compliant servlet runner since myfaces relies on the latest JSP and Servlet implementations (as defined by the spec) The blank application should get you kickstarted and the tomahawk build should give you an overview which components work. Have much fun with myfaces 1.2 As for a short explanation on how to get the build simply check out myfaces and do a mvn clean pack -Djsf=12 on the examples and it will configure everything for myfaces 1.2 a -Djsf=ri12 should make the packing for the ri according to Bruno. I will add a wiki page the next few days explaining everything so that people have an easier time to kickstart with myfaces 1.2. Werner
Re: MyFaces 1.2 + Tomahawk Kickstart was: Re: Myfaces 1.2.0 setup issues (again)
Wolf Benz schrieb: Great work Werner. A true added value. This is smth useful we can all start from. -Wolf Don´t thank me, give Bruno the credits, he added the hooks for jsf=12 in the myfaces build process so that it is easy to get kickstart projects which are jsf12 enabled out of the box. ;-)
Re: MyFaces 1.2 + Tomahawk Kickstart was: Re: Myfaces 1.2.0 setup issues (again)
Hey hey, we are a community here, credits go for all. We all write our bits and pieces here and there and it is the combination of all them what matters :-) Cheers, Bruno On 24/07/07, Werner Punz [EMAIL PROTECTED] wrote: Wolf Benz schrieb: Great work Werner. A true added value. This is smth useful we can all start from. -Wolf Don´t thank me, give Bruno the credits, he added the hooks for jsf=12 in the myfaces build process so that it is easy to get kickstart projects which are jsf12 enabled out of the box. ;-)
Re: MyFaces 1.2 + Tomahawk Kickstart was: Re: Myfaces 1.2.0 setup issues (again)
Guys, you got me all misty eyed.When's the first Apache Hug Fest / Myfaces Love Parade? ;-) MyFaces may not be the RI for JSF, it certainly smells like the RI for a dev community ;-) Kudos, -Wolf On 7/24/07, Bruno Aranda [EMAIL PROTECTED] wrote: Hey hey, we are a community here, credits go for all. We all write our bits and pieces here and there and it is the combination of all them what matters :-) Cheers, Bruno On 24/07/07, Werner Punz [EMAIL PROTECTED] wrote: Wolf Benz schrieb: Great work Werner. A true added value. This is smth useful we can all start from. -Wolf Don´t thank me, give Bruno the credits, he added the hooks for jsf=12 in the myfaces build process so that it is easy to get kickstart projects which are jsf12 enabled out of the box. ;-)
Re: Myfaces 1.2.0 setup issues (again)
Ok I did some testing on friday, as it seems there really are issues the main problem is, I could not nail them down entirely, we speak of different problems here a) The simple examples caused problems with the added web.xml injected bean in jetty (jetty does not seem to have implemented that stuff correctly) once removed it ran. This is an issue or testcase introduced by the geronimo guys, and not a problem of myfaces but a problem of jetty. Once the injection code was removed everything was running fine on Tomcat and Jetty. b) We have dependencies into commons-el from Tomahawk which were introduced by the shared project. (I could not really remove it since I didnt know exactly what the affected code was doing, any el experts here who can remove the code properly?) We need to remove that, there is a huge el clash if you introduce that one on jsp level (the bug already is covered in the bug db) And there are some jasper related issues, which might be caused by the commons-el, I am not sure, but jasper chokes big time on the tomahawk examples, which is a good indicator towards some el clashes or pending jasper issues, I assume it is the second since Matthias, since Trinidad runs fine, which also uses jasper and JSP. Funny thing is, while we cannot do anything about a) except for not using annotation based injection on jetty (which nobody uses for now anyway) for b) I really must say, if you use Tomahawk, for now, use facelets the problems are all on jsp/el level, which facelets provides its own stack, hence no problems should be there if used (and it seems to work fine). The problems will be resolved soon, so have patience for now. This seems to collide with the findings on the net, all projects which where/are facelets based seem to work fine all jsp projects moved up seem to run into issues. (Hence Matt ran into almost no issues at all, same for me, I moved an old facelets based project up in no time) Also use the latest Trunk of MyFaces 1.2, Matthias currently is fixing some bugs in there. Werner Martin Marinschek schrieb: Hear, hear! regards, Martin On 7/21/07, *Bruno Aranda* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi, A lot of testing was done after deciding that MyFaces 1.2 could be released. A part from this, the TCK is passed both in tomcat and in jetty. Tomahawk simple examples can be tested with tomahawk 1.2 right away: - Checkout the tomahawk sources and go to the tomahawk/examples/simple folder - Run the examples with mvn -PjettyConfig -Djsf=12 jetty:run Then, you will have jetty running the tomahawk simple examples with MyFaces 1.2. Of course, not everything is covered by the tests and examples we have and it is normal that some bugs appear in the first version when tested with the different environments, and I don't just mean MyFaces bugs, as it can be other bugs with jetty or tomcat that have never been using a different JSF implementation than the RI. We are working on fixing all the issues we see in MyFaces, and here the help of the community is welcome to test everything in the different setups and environments. It is the community that make MyFaces such a powerful implementation and not only this, having a powerful 1.1 implementation of JSF even the JSF RI was forced to improve (and it really has improved). This is where having two main players implementing the JSF Spec is beneficial for everybody. We work hard in both sides to ensure compatibility while we try to make the most performant and stable implementation. Here, in MyFaces, we are of the opinion of releasing sooner rather than later, and as often as we can. This is why we will release a new MyFaces version as soon as we fix some of the bugs in the first 1.2 release, and so on. Here, everybody can help testing it in the different environment and filling JIRA issues, and even giving opinions and submitting patches! MyFaces is built for everybody by everybody, or at least this is the idea. And all ideas and suggestions are welcome. We, the core developers of MyFaces, work on it because we love it :-) Even when the poor user that tries to use our bits complains (oh! how do we enjoy seeing users suffering when trying to use something we have been weeks developing and spending many sleepless nights while trying to find the equilibrium between job, family and our passion), the complaints of the user are taken and given a shape, so the next version out improves. So, in conclusion (and someone should take the keyboard from me!) thanks for trying this first version of MyFaces 1.2, finding the bugs of MyFaces, tomcat and jetty, adding your experiences in the wiki and filling JIRA issues. On the compatibility side, tomahawk is going to be branched soon to be adapted to JSF
Re: Myfaces 1.2.0 setup issues (again)
Funny thing is, while we cannot do anything about a) except for not using annotation based injection on jetty (which nobody uses for now anyway) can you open an issue, with you details? http://jira.codehaus.org/browse/JETTY Thx, Matthias for b) I really must say, if you use Tomahawk, for now, use facelets the problems are all on jsp/el level, which facelets provides its own stack, hence no problems should be there if used (and it seems to work fine). The problems will be resolved soon, so have patience for now. This seems to collide with the findings on the net, all projects which where/are facelets based seem to work fine all jsp projects moved up seem to run into issues. (Hence Matt ran into almost no issues at all, same for me, I moved an old facelets based project up in no time) Also use the latest Trunk of MyFaces 1.2, Matthias currently is fixing some bugs in there. Werner Martin Marinschek schrieb: Hear, hear! regards, Martin On 7/21/07, *Bruno Aranda* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi, A lot of testing was done after deciding that MyFaces 1.2 could be released. A part from this, the TCK is passed both in tomcat and in jetty. Tomahawk simple examples can be tested with tomahawk 1.2 right away: - Checkout the tomahawk sources and go to the tomahawk/examples/simple folder - Run the examples with mvn -PjettyConfig -Djsf=12 jetty:run Then, you will have jetty running the tomahawk simple examples with MyFaces 1.2. Of course, not everything is covered by the tests and examples we have and it is normal that some bugs appear in the first version when tested with the different environments, and I don't just mean MyFaces bugs, as it can be other bugs with jetty or tomcat that have never been using a different JSF implementation than the RI. We are working on fixing all the issues we see in MyFaces, and here the help of the community is welcome to test everything in the different setups and environments. It is the community that make MyFaces such a powerful implementation and not only this, having a powerful 1.1 implementation of JSF even the JSF RI was forced to improve (and it really has improved). This is where having two main players implementing the JSF Spec is beneficial for everybody. We work hard in both sides to ensure compatibility while we try to make the most performant and stable implementation. Here, in MyFaces, we are of the opinion of releasing sooner rather than later, and as often as we can. This is why we will release a new MyFaces version as soon as we fix some of the bugs in the first 1.2 release, and so on. Here, everybody can help testing it in the different environment and filling JIRA issues, and even giving opinions and submitting patches! MyFaces is built for everybody by everybody, or at least this is the idea. And all ideas and suggestions are welcome. We, the core developers of MyFaces, work on it because we love it :-) Even when the poor user that tries to use our bits complains (oh! how do we enjoy seeing users suffering when trying to use something we have been weeks developing and spending many sleepless nights while trying to find the equilibrium between job, family and our passion), the complaints of the user are taken and given a shape, so the next version out improves. So, in conclusion (and someone should take the keyboard from me!) thanks for trying this first version of MyFaces 1.2, finding the bugs of MyFaces, tomcat and jetty, adding your experiences in the wiki and filling JIRA issues. On the compatibility side, tomahawk is going to be branched soon to be adapted to JSF 1.2 while including a completely performance overhaul (by using the trinidad state management capabilities). But, the current tomahawk should work for any JSF 1.2 implementation, so, if some component doesn't, that is considered a bug. Cheers, Bruno :-) On 21/07/07, Martin Marinschek [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: I am of the opinion that Bruno tested the full set of MyFaces examples before he said we're good for a release. So I'd also want to hear what Bruno has to say about this. regards, Martin On 7/20/07, Werner Punz [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Wolf Benz schrieb: I am currently trying to nail down the bugs I am still not sure about everything, but as it seems there is lots of weird stuff going on -- I'm glad you've found that out as well. Quite frustrating if you get the impression stuff only jamms on your PC. in the various app servers (most of them unified el
Re: Myfaces 1.2.0 setup issues (again)
Matthias Wessendorf schrieb: Funny thing is, while we cannot do anything about a) except for not using annotation based injection on jetty (which nobody uses for now anyway) can you open an issue, with you details? http://jira.codehaus.org/browse/JETTY Certainly, this evening. I have to get the full error (my test setup is at home) Werner
Re: Myfaces 1.2.0 setup issues (again)
I suspect we could just reimplement the coercion stuff we are getting from commons-el? regards, Martin On 7/23/07, Werner Punz [EMAIL PROTECTED] wrote: Matthias Wessendorf schrieb: Funny thing is, while we cannot do anything about a) except for not using annotation based injection on jetty (which nobody uses for now anyway) can you open an issue, with you details? http://jira.codehaus.org/browse/JETTY Certainly, this evening. I have to get the full error (my test setup is at home) Werner -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
Re: Myfaces 1.2.0 setup issues (again)
Yes, btw. Bruno just told me there already is a myfaces 1.2 related switch in the maven build to kickstart the tomahawk examples with myfaces 1.2 and tomcat I am giving it a try as we speak mvn clean package cargo:start -Djsf=12 Werner Martin Marinschek schrieb: I suspect we could just reimplement the coercion stuff we are getting from commons-el? regards, Martin On 7/23/07, *Werner Punz* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Matthias Wessendorf schrieb: Funny thing is, while we cannot do anything about a) except for not using annotation based injection on jetty (which nobody uses for now anyway) can you open an issue, with you details? http://jira.codehaus.org/browse/JETTY Certainly, this evening. I have to get the full error (my test setup is at home) Werner -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
Re: Myfaces 1.2.0 setup issues (again)
Werner Punz schrieb: Yes, btw. Bruno just told me there already is a myfaces 1.2 related switch in the maven build to kickstart the tomahawk examples with myfaces 1.2 and tomcat I am giving it a try as we speak mvn clean package cargo:start -Djsf=12 Ok thanks to Brunos advice I got a working configuration, I will post a link once I am at home (which is at 9pm gmt+1) The problems were indeed caused by some dependencies into old stuff or a missing jar. Following configuration works for Tomahawk: Checkout the tomcahak examples and do a build via -Djsf=12 then you will get a working war. There seems to be some dependencies into following libs which seem to be weird: a) jstl1.1.0 and 1-2 at the same time b commons-el 1.0 (which is a total clash with the jee5 el) for a) you can remove the jstl1.1 in this case it is not needed there is a slight build bug, anyway if you do a clean package you will get a working war which should be enough to kickstart with tomcat. :-) I will post a working war in a few hours to get you guys up and running. (Once I am at home), and I also will add a wiki article for better documentation. Cheers Werner
Re: Myfaces 1.2.0 setup issues (again)
I have to say, all this is on the latest trunk of myfaces, I dont know if it works with the release, since Matthias was eliminating some bugs the last few days. Werner Werner Punz schrieb: Werner Punz schrieb: Yes, btw. Bruno just told me there already is a myfaces 1.2 related switch in the maven build to kickstart the tomahawk examples with myfaces 1.2 and tomcat I am giving it a try as we speak mvn clean package cargo:start -Djsf=12 Ok thanks to Brunos advice I got a working configuration, I will post a link once I am at home (which is at 9pm gmt+1) The problems were indeed caused by some dependencies into old stuff or a missing jar. Following configuration works for Tomahawk: Checkout the tomcahak examples and do a build via -Djsf=12 then you will get a working war. There seems to be some dependencies into following libs which seem to be weird: a) jstl1.1.0 and 1-2 at the same time b commons-el 1.0 (which is a total clash with the jee5 el) for a) you can remove the jstl1.1 in this case it is not needed there is a slight build bug, anyway if you do a clean package you will get a working war which should be enough to kickstart with tomcat. :-) I will post a working war in a few hours to get you guys up and running. (Once I am at home), and I also will add a wiki article for better documentation. Cheers Werner
Re: Myfaces 1.2.0 setup issues (again)
release often, release early ... :-) On 7/23/07, Werner Punz [EMAIL PROTECTED] wrote: I have to say, all this is on the latest trunk of myfaces, I dont know if it works with the release, since Matthias was eliminating some bugs the last few days. Werner Werner Punz schrieb: Werner Punz schrieb: Yes, btw. Bruno just told me there already is a myfaces 1.2 related switch in the maven build to kickstart the tomahawk examples with myfaces 1.2 and tomcat I am giving it a try as we speak mvn clean package cargo:start -Djsf=12 Ok thanks to Brunos advice I got a working configuration, I will post a link once I am at home (which is at 9pm gmt+1) The problems were indeed caused by some dependencies into old stuff or a missing jar. Following configuration works for Tomahawk: Checkout the tomcahak examples and do a build via -Djsf=12 then you will get a working war. There seems to be some dependencies into following libs which seem to be weird: a) jstl1.1.0 and 1-2 at the same time b commons-el 1.0 (which is a total clash with the jee5 el) for a) you can remove the jstl1.1 in this case it is not needed there is a slight build bug, anyway if you do a clean package you will get a working war which should be enough to kickstart with tomcat. :-) I will post a working war in a few hours to get you guys up and running. (Once I am at home), and I also will add a wiki article for better documentation. Cheers Werner -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ mail: matzew-at-apache-dot-org
MyFaces 1.2 + Tomahawk Kickstart was: Re: Myfaces 1.2.0 setup issues (again)
Matthias Wessendorf schrieb: release often, release early ... :-) Ok guys I am dropping the tomahawk builds and the blank application as well as a working myfaces 1.2 sandbox war into http://people.apache.org/~werpu/ as we speak, first of all there is a slight build error, once extracted you safely can remove the jstl-1.1.jar from the WEB-INF/lib the wars should work out of the box on a tomcat 6 install with a jdk5+ most tomahawk components seem to work, the same goes for the sandbox, 3-4 fail on tomahawk, and the same on the sandbox for various reasons (most of them are slight programming errors, or misuse of the 1.1 spec to achieve a certain functionality) Note, all this wont work with jdk 1.4 or a non JEE5 compliant servlet runner since myfaces relies on the latest JSP and Servlet implementations (as defined by the spec) The blank application should get you kickstarted and the tomahawk build should give you an overview which components work. Have much fun with myfaces 1.2 As for a short explanation on how to get the build simply check out myfaces and do a mvn clean pack -Djsf=12 on the examples and it will configure everything for myfaces 1.2 a -Djsf=ri12 should make the packing for the ri according to Bruno. I will add a wiki page the next few days explaining everything so that people have an easier time to kickstart with myfaces 1.2. Werner
Re: MyFaces 1.2 + Tomahawk Kickstart was: Re: Myfaces 1.2.0 setup issues (again)
Very nice, thanks ! On 7/23/07, Werner Punz [EMAIL PROTECTED] wrote: Matthias Wessendorf schrieb: release often, release early ... :-) Ok guys I am dropping the tomahawk builds and the blank application as well as a working myfaces 1.2 sandbox war into http://people.apache.org/~werpu/ as we speak, first of all there is a slight build error, once extracted you safely can remove the jstl-1.1.jar from the WEB-INF/lib the wars should work out of the box on a tomcat 6 install with a jdk5+ most tomahawk components seem to work, the same goes for the sandbox, 3-4 fail on tomahawk, and the same on the sandbox for various reasons (most of them are slight programming errors, or misuse of the 1.1 spec to achieve a certain functionality) Note, all this wont work with jdk 1.4 or a non JEE5 compliant servlet runner since myfaces relies on the latest JSP and Servlet implementations (as defined by the spec) The blank application should get you kickstarted and the tomahawk build should give you an overview which components work. Have much fun with myfaces 1.2 As for a short explanation on how to get the build simply check out myfaces and do a mvn clean pack -Djsf=12 on the examples and it will configure everything for myfaces 1.2 a -Djsf=ri12 should make the packing for the ri according to Bruno. I will add a wiki page the next few days explaining everything so that people have an easier time to kickstart with myfaces 1.2. Werner -- Grant Smith
Re: MyFaces 1.2 + Tomahawk Kickstart was: Re: Myfaces 1.2.0 setup issues (again)
So the outcome is that generally it works? What was the difference in the setup then? regards, Martin On 7/23/07, Grant Smith [EMAIL PROTECTED] wrote: Very nice, thanks ! On 7/23/07, Werner Punz [EMAIL PROTECTED] wrote: Matthias Wessendorf schrieb: release often, release early ... :-) Ok guys I am dropping the tomahawk builds and the blank application as well as a working myfaces 1.2 sandbox war into http://people.apache.org/~werpu/ http://people.apache.org/%7Ewerpu/ as we speak, first of all there is a slight build error, once extracted you safely can remove the jstl-1.1.jar from the WEB-INF/lib the wars should work out of the box on a tomcat 6 install with a jdk5+ most tomahawk components seem to work, the same goes for the sandbox, 3-4 fail on tomahawk, and the same on the sandbox for various reasons (most of them are slight programming errors, or misuse of the 1.1 spec to achieve a certain functionality) Note, all this wont work with jdk 1.4 or a non JEE5 compliant servlet runner since myfaces relies on the latest JSP and Servlet implementations (as defined by the spec) The blank application should get you kickstarted and the tomahawk build should give you an overview which components work. Have much fun with myfaces 1.2 As for a short explanation on how to get the build simply check out myfaces and do a mvn clean pack -Djsf=12 on the examples and it will configure everything for myfaces 1.2 a -Djsf=ri12 should make the packing for the ri according to Bruno. I will add a wiki page the next few days explaining everything so that people have an easier time to kickstart with myfaces 1.2. Werner -- Grant Smith -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
Re: Myfaces 1.2.0 setup issues (again)
I am of the opinion that Bruno tested the full set of MyFaces examples before he said we're good for a release. So I'd also want to hear what Bruno has to say about this. regards, Martin On 7/20/07, Werner Punz [EMAIL PROTECTED] wrote: Wolf Benz schrieb: I am currently trying to nail down the bugs I am still not sure about everything, but as it seems there is lots of weird stuff going on -- I'm glad you've found that out as well. Quite frustrating if you get the impression stuff only jamms on your PC. in the various app servers (most of them unified el related so far... jetty choked on me currently by tring to push a simple example) All I can say is dont spend too much time yet to get this release running better wait for a 2.0.1 release if things do not work out quickly. -- Too bad. If simple apps don't work perhaps the release should have better been postponed a little, as releases cannot be pulled back. Does anyone has an informed idea on when this release would see the (public)light? Wolf I cannot give dates since I am not an implementor, but some bugs I found so far were not myfaces related, one being a not fully implemented servlet spec in jetty. The plan however to my knowledge is that a 1.2.01 (sorry for the version mixup) is pushed out rather sooner than later. The funny thing is, that I have a rather complicated implementation which I was able to upgrade in no time, but that one was relying on facelets, which seems to bypass a lot of the JEE stuff (el, jsp etc...) It is more the simple jsp stuff which seems to cause problems ;-) -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
Re: Myfaces 1.2.0 setup issues (again)
Hi, A lot of testing was done after deciding that MyFaces 1.2 could be released. A part from this, the TCK is passed both in tomcat and in jetty. Tomahawk simple examples can be tested with tomahawk 1.2 right away: - Checkout the tomahawk sources and go to the tomahawk/examples/simple folder - Run the examples with mvn -PjettyConfig -Djsf=12 jetty:run Then, you will have jetty running the tomahawk simple examples with MyFaces 1.2. Of course, not everything is covered by the tests and examples we have and it is normal that some bugs appear in the first version when tested with the different environments, and I don't just mean MyFaces bugs, as it can be other bugs with jetty or tomcat that have never been using a different JSF implementation than the RI. We are working on fixing all the issues we see in MyFaces, and here the help of the community is welcome to test everything in the different setups and environments. It is the community that make MyFaces such a powerful implementation and not only this, having a powerful 1.1 implementation of JSF even the JSF RI was forced to improve (and it really has improved). This is where having two main players implementing the JSF Spec is beneficial for everybody. We work hard in both sides to ensure compatibility while we try to make the most performant and stable implementation. Here, in MyFaces, we are of the opinion of releasing sooner rather than later, and as often as we can. This is why we will release a new MyFaces version as soon as we fix some of the bugs in the first 1.2 release, and so on. Here, everybody can help testing it in the different environment and filling JIRA issues, and even giving opinions and submitting patches! MyFaces is built for everybody by everybody, or at least this is the idea. And all ideas and suggestions are welcome. We, the core developers of MyFaces, work on it because we love it :-) Even when the poor user that tries to use our bits complains (oh! how do we enjoy seeing users suffering when trying to use something we have been weeks developing and spending many sleepless nights while trying to find the equilibrium between job, family and our passion), the complaints of the user are taken and given a shape, so the next version out improves. So, in conclusion (and someone should take the keyboard from me!) thanks for trying this first version of MyFaces 1.2, finding the bugs of MyFaces, tomcat and jetty, adding your experiences in the wiki and filling JIRA issues. On the compatibility side, tomahawk is going to be branched soon to be adapted to JSF 1.2 while including a completely performance overhaul (by using the trinidad state management capabilities). But, the current tomahawk should work for any JSF 1.2 implementation, so, if some component doesn't, that is considered a bug. Cheers, Bruno :-) On 21/07/07, Martin Marinschek [EMAIL PROTECTED] wrote: I am of the opinion that Bruno tested the full set of MyFaces examples before he said we're good for a release. So I'd also want to hear what Bruno has to say about this. regards, Martin On 7/20/07, Werner Punz [EMAIL PROTECTED] wrote: Wolf Benz schrieb: I am currently trying to nail down the bugs I am still not sure about everything, but as it seems there is lots of weird stuff going on -- I'm glad you've found that out as well. Quite frustrating if you get the impression stuff only jamms on your PC. in the various app servers (most of them unified el related so far... jetty choked on me currently by tring to push a simple example) All I can say is dont spend too much time yet to get this release running better wait for a 2.0.1 release if things do not work out quickly. -- Too bad. If simple apps don't work perhaps the release should have better been postponed a little, as releases cannot be pulled back. Does anyone has an informed idea on when this release would see the (public)light? Wolf I cannot give dates since I am not an implementor, but some bugs I found so far were not myfaces related, one being a not fully implemented servlet spec in jetty. The plan however to my knowledge is that a 1.2.01 (sorry for the version mixup) is pushed out rather sooner than later. The funny thing is, that I have a rather complicated implementation which I was able to upgrade in no time, but that one was relying on facelets, which seems to bypass a lot of the JEE stuff (el, jsp etc...) It is more the simple jsp stuff which seems to cause problems ;-) -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
Re: Myfaces 1.2.0 setup issues (again)
Hear, hear! regards, Martin On 7/21/07, Bruno Aranda [EMAIL PROTECTED] wrote: Hi, A lot of testing was done after deciding that MyFaces 1.2 could be released. A part from this, the TCK is passed both in tomcat and in jetty. Tomahawk simple examples can be tested with tomahawk 1.2 right away: - Checkout the tomahawk sources and go to the tomahawk/examples/simple folder - Run the examples with mvn -PjettyConfig -Djsf=12 jetty:run Then, you will have jetty running the tomahawk simple examples with MyFaces 1.2. Of course, not everything is covered by the tests and examples we have and it is normal that some bugs appear in the first version when tested with the different environments, and I don't just mean MyFaces bugs, as it can be other bugs with jetty or tomcat that have never been using a different JSF implementation than the RI. We are working on fixing all the issues we see in MyFaces, and here the help of the community is welcome to test everything in the different setups and environments. It is the community that make MyFaces such a powerful implementation and not only this, having a powerful 1.1 implementation of JSF even the JSF RI was forced to improve (and it really has improved). This is where having two main players implementing the JSF Spec is beneficial for everybody. We work hard in both sides to ensure compatibility while we try to make the most performant and stable implementation. Here, in MyFaces, we are of the opinion of releasing sooner rather than later, and as often as we can. This is why we will release a new MyFaces version as soon as we fix some of the bugs in the first 1.2 release, and so on. Here, everybody can help testing it in the different environment and filling JIRA issues, and even giving opinions and submitting patches! MyFaces is built for everybody by everybody, or at least this is the idea. And all ideas and suggestions are welcome. We, the core developers of MyFaces, work on it because we love it :-) Even when the poor user that tries to use our bits complains (oh! how do we enjoy seeing users suffering when trying to use something we have been weeks developing and spending many sleepless nights while trying to find the equilibrium between job, family and our passion), the complaints of the user are taken and given a shape, so the next version out improves. So, in conclusion (and someone should take the keyboard from me!) thanks for trying this first version of MyFaces 1.2, finding the bugs of MyFaces, tomcat and jetty, adding your experiences in the wiki and filling JIRA issues. On the compatibility side, tomahawk is going to be branched soon to be adapted to JSF 1.2 while including a completely performance overhaul (by using the trinidad state management capabilities). But, the current tomahawk should work for any JSF 1.2 implementation, so, if some component doesn't, that is considered a bug. Cheers, Bruno :-) On 21/07/07, Martin Marinschek [EMAIL PROTECTED] wrote: I am of the opinion that Bruno tested the full set of MyFaces examples before he said we're good for a release. So I'd also want to hear what Bruno has to say about this. regards, Martin On 7/20/07, Werner Punz [EMAIL PROTECTED] wrote: Wolf Benz schrieb: I am currently trying to nail down the bugs I am still not sure about everything, but as it seems there is lots of weird stuff going on -- I'm glad you've found that out as well. Quite frustrating if you get the impression stuff only jamms on your PC. in the various app servers (most of them unified el related so far... jetty choked on me currently by tring to push a simple example) All I can say is dont spend too much time yet to get this release running better wait for a 2.0.1 release if things do not work out quickly. -- Too bad. If simple apps don't work perhaps the release should have better been postponed a little, as releases cannot be pulled back. Does anyone has an informed idea on when this release would see the (public)light? Wolf I cannot give dates since I am not an implementor, but some bugs I found so far were not myfaces related, one being a not fully implemented servlet spec in jetty. The plan however to my knowledge is that a 1.2.01 (sorry for the version mixup) is pushed out rather sooner than later. The funny thing is, that I have a rather complicated implementation which I was able to upgrade in no time, but that one was relying on facelets, which seems to bypass a lot of the JEE stuff (el, jsp etc...) It is more the simple jsp stuff which seems to cause problems ;-) -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
Re: Myfaces 1.2.0 setup issues (again)
Ok I talked with Matthias regarding all ths first of all there seems to be an issue with tomcat 6 regarding JSTL compatibility Tomahawk seems to have hooks into it. Matthias told me that Jetty works, Tomcat doesnt (seems to be Tomcats fault or jaspers in Tomcat 6.0.13) The problem goes away as soon as you use facelets, since facelets does not require JSP. (Hence my application works) With Facelets also the usage of Tomcat 6 is possible. Werner Werner Punz schrieb: Ok sorry for this, as it seems there is an issue in the examples with Tomcat 6 and the jstl needed by the sandbox examples, my app was not affected since it does not use the jstl (and facelets work fine) can anyone confirm this, not sure why the jstl is in the tomahawk examples at all. If anyone of the myfaces 1.2 authors could jump in here I would be grateful ;-) The funny thing is in my facelets/spring configuration I am not affected not sure where the problem is, but it must be a mixture of jstl dependencies which and tomcat 6 :-) Werner Punz schrieb: Wolf Benz schrieb: Hi List It's very cool MyFaces 1.2 finally got out of the door but... It's again a true pain setting MyFaces up correctly before it works... (more than it should). I remember it took me an entire week before I had MyFaces 1.x configured correctly with the Extension Filter etc. What a waste of time :-( In the mean time, other sites have helped out and put a proper Tutorial or a complete blank app online but this major new release demands renewed examples and ... is a chance for e renewed approach. Yet, with MyFaces 1.2.0 out, I see the old the same mistakes are made again: - no examples - no info on the web.xml (like: should it specify servlet container v 2.5 now?) - no info on the faces-config.xml (like: should it specify http://java.sun.com/dtd/web-facesconfig_1_1.dtd or v.1.2?) - no info on what jars are exactly required - no compatibility matrix (like: works with Tomcat6? Can you use Tomahawk (e.g. of version 1.6) together with MyFaces1.2? ... Hi Wolf, first of all sorry for the lack of examples and documentation for now anyway. I just moved a project testwise up to the current myfaces and sort of was pleasantly surprised how good it went, so some help here from my side: First of all MyFaces 1.2 needs the latest JEE5 implementations of the servlet jsp/servlet api and at least java 5 (sorry but that is a limitation introduced by JSF 1.2 itself) So what you have to do, the configuration basically stayed the same from what I could tell, I didnt have to alter my old web.xml You just have to make sure you run on a container which provides the latest standard (it was tomcat 6 in my case) then I removed all jars wich referenced jsp apis, el apis and jasper, or serlvet apis, I moved the myfaces libs up to the latest versions as well as their dependencies (which come in in the pack) the last problem and this is a bug in Tomahawk, which I am filing at the moment, is a dependency into commons-el, you have to readd the jar if you use the sandbox and tomahawk unfortunately, I dont know if this can cause sideffects, but so far I couldnt notice one (but I am on facelets anyway) Once this is done it should run. I get the impression the jars are just dumped online and the makers have a great time looking at how users have a terrible time figuring it all out themselves... Actually no it definitely is not like that, we are no sadists, it is more along the lines, that the implementation is way overdue timewise and it had to get out asap, so that the server programmers can start using it. Expect the situation to improve soon. (Btw. thanks to all the guys who finally got the release out) As I cannot image no one on this list has such example, could someone take the effort of posting the jar online to help all the rest of us out? My setup is: Tomcat6, MyFaces 1.2, Tomahawk(if possible in combination with MF1.2.0 - also this info is not online) I guess this setup would currently the most common one. I spent the last 2 days (starting from my old MF 1.1.5/Toma1.1.5 app on Tomcat 5) trying to migrate it to that setup but to no avail. Actually if you want contact me either via mail, or via google talk (same address as posted here) or via icq 46949386 I am yet a mere user of MyFaces 1.2 myself but I might be able to help you out to get it running. Cheers Werner
Re: Myfaces 1.2.0 setup issues (again)
Werner Punz schrieb: Ok I talked with Matthias regarding all ths first of all there seems to be an issue with tomcat 6 regarding JSTL compatibility Tomahawk seems to have hooks into it. Matthias told me that Jetty works, Tomcat doesnt (seems to be Tomcats fault or jaspers in Tomcat 6.0.13) The problem goes away as soon as you use facelets, since facelets does not require JSP. (Hence my application works) With Facelets also the usage of Tomcat 6 is possible. Werner Ok I just got in a correction of Matthias, as it seems I cannot confirm jetty yet. Anyway, I will do furhter testing this afternoon to circle the entire thing in a little bit (also I will try jetty personally) All I personally can say for now, is that I can confirm that the combination of Tomcat 6 MyFaces 1.2 and Facelets work as they should. please watch https://issues.apache.org/jira/browse/MYFACES-1682 for further comments on this.
Re: Myfaces 1.2.0 setup issues (again)
Ok I just got in a correction of Matthias, as it seems I cannot confirm jetty yet. Anyway, I will do furhter testing this afternoon to circle the entire thing in a little bit (also I will try jetty personally) All I personally can say for now, is that I can confirm that the combination of Tomcat 6 MyFaces 1.2 and Facelets work as they should. please watch https://issues.apache.org/jira/browse/MYFACES-1682 for further comments on this. so, I noticed the TLD thing on ([1]) in tomcat 6.0.13 with and without tomahawk. Not in Jetty 6.1.2rc0 . -Matthias [1] https://issues.apache.org/jira/browse/MYFACES-1682 -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ mail: matzew-at-apache-dot-org
Re: Myfaces 1.2.0 setup issues (again)
Hi allThanks for the help so far guys. After yesterday's struggling, I wasn't really in the mood today to pick it up again so quickly. Will try again this WE. Short question aside: I've got nothing against facelets (quite the contrary), but I understand from previous postings the combo Tomcat6 - MF120 - Tomahawk - JSP is a dead end. I think this is a problem as I guess most users will use this combo. Tomcat6 is kinda a standard and if you don't need Tomahawk, why not just use the RI... (MF could learn smth from their easy setup -- I think there's great value in defaulting much more so that the web.xml can remain much easier than MF makes it now) Facelets is better than JSP yet most users still use JSP... Certainly as I guess what most users will forst attempt(like myself) is migrate old apps to the new MF std. Or does JSP work if you just don't use JSTL? How good are your contacts with the Apache Tomcat team to perhaps address this issue in an incremental Tomcat release? (should this be the best way to solve this decoupling) Wolf On 7/20/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: Ok I just got in a correction of Matthias, as it seems I cannot confirm jetty yet. Anyway, I will do furhter testing this afternoon to circle the entire thing in a little bit (also I will try jetty personally) All I personally can say for now, is that I can confirm that the combination of Tomcat 6 MyFaces 1.2 and Facelets work as they should. please watch https://issues.apache.org/jira/browse/MYFACES-1682 for further comments on this. so, I noticed the TLD thing on ([1]) in tomcat 6.0.13 with and without tomahawk. Not in Jetty 6.1.2rc0 . -Matthias [1] https://issues.apache.org/jira/browse/MYFACES-1682 -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ mail: matzew-at-apache-dot-org
Re: Myfaces 1.2.0 setup issues (again)
Hi Wolf I am currently trying to nail down the bugs I am still not sure about everything, but as it seems there is lots of weird stuff going on in the various app servers (most of them unified el related so far... jetty choked on me currently by tring to push a simple example) All I can say is dont spend too much time yet to get this release running better wait for a 2.0.1 release if things do not work out quickly. Werner Wolf Benz schrieb: Hi all Thanks for the help so far guys. After yesterday's struggling, I wasn't really in the mood today to pick it up again so quickly. Will try again this WE. Short question aside: I've got nothing against facelets (quite the contrary), but I understand from previous postings the combo Tomcat6 - MF120 - Tomahawk - JSP is a dead end. I think this is a problem as I guess most users will use this combo. Tomcat6 is kinda a standard and if you don't need Tomahawk, why not just use the RI... (MF could learn smth from their easy setup -- I think there's great value in defaulting much more so that the web.xml can remain much easier than MF makes it now) Facelets is better than JSP yet most users still use JSP... Certainly as I guess what most users will forst attempt(like myself) is migrate old apps to the new MF std. Or does JSP work if you just don't use JSTL? How good are your contacts with the Apache Tomcat team to perhaps address this issue in an incremental Tomcat release? (should this be the best way to solve this decoupling) Wolf On 7/20/07, *Matthias Wessendorf* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Ok I just got in a correction of Matthias, as it seems I cannot confirm jetty yet. Anyway, I will do furhter testing this afternoon to circle the entire thing in a little bit (also I will try jetty personally) All I personally can say for now, is that I can confirm that the combination of Tomcat 6 MyFaces 1.2 and Facelets work as they should. please watch https://issues.apache.org/jira/browse/MYFACES-1682 for further comments on this. so, I noticed the TLD thing on ([1]) in tomcat 6.0.13 with and without tomahawk. Not in Jetty 6.1.2rc0 . -Matthias [1] https://issues.apache.org/jira/browse/MYFACES-1682 -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ mail: matzew-at-apache-dot-org
Re: Myfaces 1.2.0 setup issues (again)
running better wait for a 2.0.1 release if things do not work out quickly. 1.2.1 ;) Werner Wolf Benz schrieb: Hi all Thanks for the help so far guys. After yesterday's struggling, I wasn't really in the mood today to pick it up again so quickly. Will try again this WE. Short question aside: I've got nothing against facelets (quite the contrary), but I understand from previous postings the combo Tomcat6 - MF120 - Tomahawk - JSP is a dead end. I think this is a problem as I guess most users will use this combo. Tomcat6 is kinda a standard and if you don't need Tomahawk, why not just use the RI... (MF could learn smth from their easy setup -- I think there's great value in defaulting much more so that the web.xml can remain much easier than MF makes it now) Facelets is better than JSP yet most users still use JSP... Certainly as I guess what most users will forst attempt(like myself) is migrate old apps to the new MF std. Or does JSP work if you just don't use JSTL? How good are your contacts with the Apache Tomcat team to perhaps address this issue in an incremental Tomcat release? (should this be the best way to solve this decoupling) Wolf On 7/20/07, *Matthias Wessendorf* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Ok I just got in a correction of Matthias, as it seems I cannot confirm jetty yet. Anyway, I will do furhter testing this afternoon to circle the entire thing in a little bit (also I will try jetty personally) All I personally can say for now, is that I can confirm that the combination of Tomcat 6 MyFaces 1.2 and Facelets work as they should. please watch https://issues.apache.org/jira/browse/MYFACES-1682 for further comments on this. so, I noticed the TLD thing on ([1]) in tomcat 6.0.13 with and without tomahawk. Not in Jetty 6.1.2rc0 . -Matthias [1] https://issues.apache.org/jira/browse/MYFACES-1682 -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ mail: matzew-at-apache-dot-org -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ mail: matzew-at-apache-dot-org
Re: Myfaces 1.2.0 setup issues (again)
I am currently trying to nail down the bugs I am still not sure about everything, but as it seems there is lots of weird stuff going on -- I'm glad you've found that out as well. Quite frustrating if you get the impression stuff only jamms on your PC. in the various app servers (most of them unified el related so far... jetty choked on me currently by tring to push a simple example) All I can say is dont spend too much time yet to get this release running better wait for a 2.0.1 release if things do not work out quickly. -- Too bad. If simple apps don't work perhaps the release should have better been postponed a little, as releases cannot be pulled back. Does anyone has an informed idea on when this release would see the (public)light? Wolf
Re: Myfaces 1.2.0 setup issues (again)
Hi fashion creators ;-),
I'm really happy for this last event, even if I'm a little late (notice it
has its advanteges to be late too ;-).
Wolf:
Tomcat6 is kinda a standard and if you don't need Tomahawk, why not just
use the RI
I'd say you're a little direct with the MyFaces team, comparing the RI and
MyFaces with all its subprojects is a little unfair comparaison seen that
the RI doesn't have to handle nor ajax features nor css beside the fact that
it's definitely less rich in its components, in addition to the fact that
MyFaces is not just Tomahawk, and that the RI is only a sort of testing
labs with no performance objectives.
On the other side, I agree with you in the fact that integrating MyFaces is
not made very easy. For me, exception messages of MyFaces are not verbose
enough to give you an orientation on what's exactly going wrong. I think
some work of catching and rethrowing more explicit and verbose exceptions
could help in all developement and integration phasis.
Just for an example on the well known exception: Base is null
It costed me nothing to add this code snippet in ValueBindingImpl:
line 461
*if* (base == *null*)
{
*throw* *new* PropertyNotFoundException(Base is null:
+ complexValue.getPrefix().*getExpressionString*() + in
expression: + complexValue.getExpressionString() );
}
line 475
*if* (base == *null*)
{
*throw* *new* PropertyNotFoundException(Base is null:
+ suffix.*getExpressionString*() + in expression: +
suffixes + for object: + complexValue.getPrefix()
.*evaluate*(variableResolver, *s_functionMapper*,
ELParserHelper.*LOGGER*) );
}
So I spend less time in searching in which page the problem is. A even
better handling would be to say in which page and which line the problem
occured (by catching this exception in a wider context). The same can be
done for testing if MyFaces is loaded correctly (a sort of self checking
utility).
Regards,
Zied
2007/7/20, Matthias Wessendorf [EMAIL PROTECTED]:
running better wait for a 2.0.1 release if things do not work out
quickly.
1.2.1 ;)
Werner
Wolf Benz schrieb:
Hi all
Thanks for the help so far guys.
After yesterday's struggling, I wasn't really in the mood today to
pick
it up again so quickly. Will try again this WE.
Short question aside:
I've got nothing against facelets (quite the contrary), but I
understand
from previous postings the combo Tomcat6 - MF120 - Tomahawk - JSP is a
dead end.
I think this is a problem as I guess most users will use this combo.
Tomcat6 is kinda a standard and if you don't need Tomahawk, why not
just
use the RI... (MF could learn smth from their easy setup -- I think
there's great value in defaulting much more so that the web.xml can
remain much easier than MF makes it now)
Facelets is better than JSP yet most users still use JSP...
Certainly as I guess what most users will forst attempt(like myself)
is
migrate old apps to the new MF std.
Or does JSP work if you just don't use JSTL?
How good are your contacts with the Apache Tomcat team to perhaps
address this issue in an incremental Tomcat release? (should this be
the
best way to solve this decoupling)
Wolf
On 7/20/07, *Matthias Wessendorf* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Ok I just got in a correction of Matthias, as it seems I cannot
confirm
jetty yet.
Anyway, I will do furhter testing this afternoon to circle the
entire
thing in a little bit (also I will try jetty personally)
All I personally can say for now, is that I can confirm that
the
combination
of Tomcat 6 MyFaces 1.2 and Facelets work as they should.
please watch https://issues.apache.org/jira/browse/MYFACES-1682
for further comments on this.
so, I noticed the TLD thing on ([1]) in tomcat 6.0.13 with and
without tomahawk.
Not in Jetty 6.1.2rc0 .
-Matthias
[1] https://issues.apache.org/jira/browse/MYFACES-1682
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
mail: matzew-at-apache-dot-org
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
mail: matzew-at-apache-dot-org
--
Zied Hamdi
zatreex.sourceforge.net
Re: Myfaces 1.2.0 setup issues (again)
Wolf Benz schrieb: I am currently trying to nail down the bugs I am still not sure about everything, but as it seems there is lots of weird stuff going on -- I'm glad you've found that out as well. Quite frustrating if you get the impression stuff only jamms on your PC. in the various app servers (most of them unified el related so far... jetty choked on me currently by tring to push a simple example) All I can say is dont spend too much time yet to get this release running better wait for a 2.0.1 release if things do not work out quickly. -- Too bad. If simple apps don't work perhaps the release should have better been postponed a little, as releases cannot be pulled back. Does anyone has an informed idea on when this release would see the (public)light? Wolf I cannot give dates since I am not an implementor, but some bugs I found so far were not myfaces related, one being a not fully implemented servlet spec in jetty. The plan however to my knowledge is that a 1.2.01 (sorry for the version mixup) is pushed out rather sooner than later. The funny thing is, that I have a rather complicated implementation which I was able to upgrade in no time, but that one was relying on facelets, which seems to bypass a lot of the JEE stuff (el, jsp etc...) It is more the simple jsp stuff which seems to cause problems ;-)
Re: Myfaces 1.2.0 setup issues (again)
Attaching some more infos, like stack trace or debug infos, would speed up things! -- I planned to make some time for that this WE. (I didn't forget your previous post!) I'll try to look at some of your issues over the weekend. -- Cool. And that's smth that can be said of this project: the user list is VERY responsive and to the point. If it weren't for that, I think I might have switched in the past already... (time, time) -Wolf
Re: Myfaces 1.2.0 setup issues (again)
Hi wolf, nobody here is having a great time looking at how users have a terrible time figuring it all out themselves. can you please file jira issues on your items ? Yes there is a minimal example out there: http://svn.apache.org/viewvc/myfaces/current12/test-webapp/ We have to add it to the next release (please file a jira issue on that) There is also a more complex demo (using Trinidad, instead of Tomahawk) (and jetty): http://code.google.com/p/facesgoodies/ (do a svn check out, since the ZIPPY is using myfaces.1.2.0-SNAPSHOT) File a jira issue on having a tomahawk-demo as well (I know that Werner did some *investments* here already) Thanks, Matthias On 7/19/07, Wolf Benz [EMAIL PROTECTED] wrote: Hi List It's very cool MyFaces 1.2 finally got out of the door but... It's again a true pain setting MyFaces up correctly before it works... (more than it should). I remember it took me an entire week before I had MyFaces 1.x configured correctly with the Extension Filter etc. What a waste of time :-( In the mean time, other sites have helped out and put a proper Tutorial or a complete blank app online but this major new release demands renewed examples and ... is a chance for e renewed approach. Yet, with MyFaces 1.2.0 out, I see the old the same mistakes are made again: - no examples - no info on the web.xml (like: should it specify servlet container v 2.5 now?) - no info on the faces-config.xml (like: should it specify http:// java.sun.com/dtd/web-facesconfig_1_1.dtd or v.1.2?) - no info on what jars are exactly required - no compatibility matrix (like: works with Tomcat6? Can you use Tomahawk (e.g. of version 1.6) together with MyFaces1.2? ... I get the impression the jars are just dumped online and the makers have a great time looking at how users have a terrible time figuring it all out themselves... As I cannot image no one on this list has such example, could someone take the effort of posting the jar online to help all the rest of us out? My setup is: Tomcat6, MyFaces 1.2, Tomahawk(if possible in combination with MF1.2.0 - also this info is not online) I guess this setup would currently the most common one. I spent the last 2 days (starting from my old MF 1.1.5/Toma1.1.5 app on Tomcat 5) trying to migrate it to that setup but to no avail. Many thanks, Wolf -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ mail: matzew-at-apache-dot-org
Re: Myfaces 1.2.0 setup issues (again)
Wolf Benz schrieb: Hi List It's very cool MyFaces 1.2 finally got out of the door but... It's again a true pain setting MyFaces up correctly before it works... (more than it should). I remember it took me an entire week before I had MyFaces 1.x configured correctly with the Extension Filter etc. What a waste of time :-( In the mean time, other sites have helped out and put a proper Tutorial or a complete blank app online but this major new release demands renewed examples and ... is a chance for e renewed approach. Yet, with MyFaces 1.2.0 out, I see the old the same mistakes are made again: - no examples - no info on the web.xml (like: should it specify servlet container v 2.5 now?) - no info on the faces-config.xml (like: should it specify http://java.sun.com/dtd/web-facesconfig_1_1.dtd or v.1.2?) - no info on what jars are exactly required - no compatibility matrix (like: works with Tomcat6? Can you use Tomahawk (e.g. of version 1.6) together with MyFaces1.2? ... Hi Wolf, first of all sorry for the lack of examples and documentation for now anyway. I just moved a project testwise up to the current myfaces and sort of was pleasantly surprised how good it went, so some help here from my side: First of all MyFaces 1.2 needs the latest JEE5 implementations of the servlet jsp/servlet api and at least java 5 (sorry but that is a limitation introduced by JSF 1.2 itself) So what you have to do, the configuration basically stayed the same from what I could tell, I didnt have to alter my old web.xml You just have to make sure you run on a container which provides the latest standard (it was tomcat 6 in my case) then I removed all jars wich referenced jsp apis, el apis and jasper, or serlvet apis, I moved the myfaces libs up to the latest versions as well as their dependencies (which come in in the pack) the last problem and this is a bug in Tomahawk, which I am filing at the moment, is a dependency into commons-el, you have to readd the jar if you use the sandbox and tomahawk unfortunately, I dont know if this can cause sideffects, but so far I couldnt notice one (but I am on facelets anyway) Once this is done it should run. I get the impression the jars are just dumped online and the makers have a great time looking at how users have a terrible time figuring it all out themselves... Actually no it definitely is not like that, we are no sadists, it is more along the lines, that the implementation is way overdue timewise and it had to get out asap, so that the server programmers can start using it. Expect the situation to improve soon. (Btw. thanks to all the guys who finally got the release out) As I cannot image no one on this list has such example, could someone take the effort of posting the jar online to help all the rest of us out? My setup is: Tomcat6, MyFaces 1.2, Tomahawk(if possible in combination with MF1.2.0 - also this info is not online) I guess this setup would currently the most common one. I spent the last 2 days (starting from my old MF 1.1.5/Toma1.1.5 app on Tomcat 5) trying to migrate it to that setup but to no avail. Actually if you want contact me either via mail, or via google talk (same address as posted here) or via icq 46949386 I am yet a mere user of MyFaces 1.2 myself but I might be able to help you out to get it running. Cheers Werner
Re: Myfaces 1.2.0 setup issues (again)
Ok sorry for this, as it seems there is an issue in the examples with Tomcat 6 and the jstl needed by the sandbox examples, my app was not affected since it does not use the jstl (and facelets work fine) can anyone confirm this, not sure why the jstl is in the tomahawk examples at all. If anyone of the myfaces 1.2 authors could jump in here I would be grateful ;-) The funny thing is in my facelets/spring configuration I am not affected not sure where the problem is, but it must be a mixture of jstl dependencies which and tomcat 6 :-) Werner Punz schrieb: Wolf Benz schrieb: Hi List It's very cool MyFaces 1.2 finally got out of the door but... It's again a true pain setting MyFaces up correctly before it works... (more than it should). I remember it took me an entire week before I had MyFaces 1.x configured correctly with the Extension Filter etc. What a waste of time :-( In the mean time, other sites have helped out and put a proper Tutorial or a complete blank app online but this major new release demands renewed examples and ... is a chance for e renewed approach. Yet, with MyFaces 1.2.0 out, I see the old the same mistakes are made again: - no examples - no info on the web.xml (like: should it specify servlet container v 2.5 now?) - no info on the faces-config.xml (like: should it specify http://java.sun.com/dtd/web-facesconfig_1_1.dtd or v.1.2?) - no info on what jars are exactly required - no compatibility matrix (like: works with Tomcat6? Can you use Tomahawk (e.g. of version 1.6) together with MyFaces1.2? ... Hi Wolf, first of all sorry for the lack of examples and documentation for now anyway. I just moved a project testwise up to the current myfaces and sort of was pleasantly surprised how good it went, so some help here from my side: First of all MyFaces 1.2 needs the latest JEE5 implementations of the servlet jsp/servlet api and at least java 5 (sorry but that is a limitation introduced by JSF 1.2 itself) So what you have to do, the configuration basically stayed the same from what I could tell, I didnt have to alter my old web.xml You just have to make sure you run on a container which provides the latest standard (it was tomcat 6 in my case) then I removed all jars wich referenced jsp apis, el apis and jasper, or serlvet apis, I moved the myfaces libs up to the latest versions as well as their dependencies (which come in in the pack) the last problem and this is a bug in Tomahawk, which I am filing at the moment, is a dependency into commons-el, you have to readd the jar if you use the sandbox and tomahawk unfortunately, I dont know if this can cause sideffects, but so far I couldnt notice one (but I am on facelets anyway) Once this is done it should run. I get the impression the jars are just dumped online and the makers have a great time looking at how users have a terrible time figuring it all out themselves... Actually no it definitely is not like that, we are no sadists, it is more along the lines, that the implementation is way overdue timewise and it had to get out asap, so that the server programmers can start using it. Expect the situation to improve soon. (Btw. thanks to all the guys who finally got the release out) As I cannot image no one on this list has such example, could someone take the effort of posting the jar online to help all the rest of us out? My setup is: Tomcat6, MyFaces 1.2, Tomahawk(if possible in combination with MF1.2.0 - also this info is not online) I guess this setup would currently the most common one. I spent the last 2 days (starting from my old MF 1.1.5/Toma1.1.5 app on Tomcat 5) trying to migrate it to that setup but to no avail. Actually if you want contact me either via mail, or via google talk (same address as posted here) or via icq 46949386 I am yet a mere user of MyFaces 1.2 myself but I might be able to help you out to get it running. Cheers Werner
