[ https://issues.jboss.org/browse/RFPL-1285?page=com.atlassian.jira.plugin.... ] Juraj Huska commented on RFPL-1285: ----------------------------------- I added projects to: https://svn.jboss.org/repos/qa/richfaces/ There are two projects, one is maven project, second is JSF project. I am also sending you an email with report. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RFPL-1285?page=com.atlassian.jira.plugin.... ] Prabhat Jha commented on RFPL-1285: ----------------------------------- Attaching list of issues reported with RF4 and JBoss Tools testing. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RFPL-1285?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on RFPL-1285 at 3/22/11 5:10 PM: ----------------------------------------------------------- If the issues reported in the attachment (copied below to facilitate seeing them w/o external editor) are still issues, they should be opened as individual JIRA against JBoss Tools 3.2.0 (see JBIDE project: https://jira.jboss.org/jira/browse/JBIDE), ostensibly scheduled to fix in 3.2.1. {quote} 1. When I was creating maven project, when I was choosing the archetype, there were as the latest version 4.0.0.20100826-M2, when I uncheck the option of showing the latest version of archetype only, the 4.0.0.Final appeared as well, the archetype was richfaces-archetype-simpleapp. 2. The Jboss Tools palette did not contain the latest taglib, so I had to added it via import menu of palette. 3. When the bean is created via annotations, the binding of bean does not work properly, for example I tried to add rich:dataTable and to bind the particular bean, I was able to find it in the file system, but I was not able to access the bean's property. When the bean was declared via XML in faces-config.xml, then I was able to access the property of that bean. 4. When I wanted to add a4j:param, there was no option of binding bean, so I had to fill attribute assignTo manually when the bean was created via annotations, when was created via XML, I was able to find it via asssingTo attribute. 5. It seems like eclipse has problems with beans created with annotations in general. 6. When the bean is created from annotations also code completion does not work. 7. When I created JSF project, and tried to add capabilities via Web Projects view, there was only RichFaces 3.3 to choose from. 8. The sample, which was created in JSF project has in templates, in particular in WebContent/templates/common.xhtml, tags do not have h: prefix before head and body tag 9.There is missing sac.jar and cssparser.jar library in the fresh JSF project and therefore there is error generated. 10.When I do not add component from palette, the reference for particular tag is not added, so parser can not find it, so then also code completion does not work. I am talking about reference to for example a4j tag. 11. There are same problems with beans created via annotations in JSF project than in maven project. {quote} was (Author: nickboldt): If the issues reported in the attachment (copied below to facilitate seeing them w/o external editor) are still issues, they should be opened as individual JIRA against JBoss Tools 3.2.0, ostensibly scheduled to fix in 3.2.1. {quote} 1. When I was creating maven project, when I was choosing the archetype, there were as the latest version 4.0.0.20100826-M2, when I uncheck the option of showing the latest version of archetype only, the 4.0.0.Final appeared as well, the archetype was richfaces-archetype-simpleapp. 2. The Jboss Tools palette did not contain the latest taglib, so I had to added it via import menu of palette. 3. When the bean is created via annotations, the binding of bean does not work properly, for example I tried to add rich:dataTable and to bind the particular bean, I was able to find it in the file system, but I was not able to access the bean's property. When the bean was declared via XML in faces-config.xml, then I was able to access the property of that bean. 4. When I wanted to add a4j:param, there was no option of binding bean, so I had to fill attribute assignTo manually when the bean was created via annotations, when was created via XML, I was able to find it via asssingTo attribute. 5. It seems like eclipse has problems with beans created with annotations in general. 6. When the bean is created from annotations also code completion does not work. 7. When I created JSF project, and tried to add capabilities via Web Projects view, there was only RichFaces 3.3 to choose from. 8. The sample, which was created in JSF project has in templates, in particular in WebContent/templates/common.xhtml, tags do not have h: prefix before head and body tag 9.There is missing sac.jar and cssparser.jar library in the fresh JSF project and therefore there is error generated. 10.When I do not add component from palette, the reference for particular tag is not added, so parser can not find it, so then also code completion does not work. I am talking about reference to for example a4j tag. 11. There are same problems with beans created via annotations in JSF project than in maven project. {quote} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RFPL-1285?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on RFPL-1285: -------------------------------------- {quote} 2. The Jboss Tools palette did not contain the latest taglib, so I had to added it via import menu of palette. {quote} Created an issue. See JBIDE-8617 {quote} 3. When the bean is created via annotations, the binding of bean does not work properly, for example I tried to add rich:dataTable and to bind the particular bean, I was able to find it in the file system, but I was not able to access the bean's property. When the bean was declared via XML in faces-config.xml, then I was able to access the property of that bean. 4. When I wanted to add a4j:param, there was no option of binding bean, so I had to fill attribute assignTo manually when the bean was created via annotations, when was created via XML, I was able to find it via asssingTo attribute. 5. It seems like eclipse has problems with beans created with annotations in general. 6. When the bean is created from annotations also code completion does not work. ... 11. There are same problems with beans created via annotations in JSF project than in maven project. {quote} Already in JIRA. See JBIDE-5045 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RFPL-1285?page=com.atlassian.jira.plugin.... ] Alexey Kazakov edited comment on RFPL-1285 at 3/22/11 7:10 PM: --------------------------------------------------------------- {quote} 8. The sample, which was created in JSF project has in templates, in particular in WebContent/templates/common.xhtml, tags do not have h: prefix before head and body tag {quote} I'm not sure I understand the problem... common.xhtml is correct if I'm looking at the right place: https://svn.jboss.org/repos/qa/richfaces/test-app-4.0.0.Final-JBoss-Tools... was (Author: akazakov): {quite} 8. The sample, which was created in JSF project has in templates, in particular in WebContent/templates/common.xhtml, tags do not have h: prefix before head and body tag {quite} I'm not sure I understand the problem... common.xhtml is correct if I'm looking at the right place: https://svn.jboss.org/repos/qa/richfaces/test-app-4.0.0.Final-JBoss-Tools... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RFPL-1285?page=com.atlassian.jira.plugin.... ] Juraj Huska commented on RFPL-1285: ----------------------------------- {quote} 8. The sample, which was created in JSF project has in templates, in particular in WebContent/templates/common.xhtml, tags do not have h: prefix before head and body tag I'm not sure I understand the problem... common.xhtml is correct if I'm looking at the right place: https://svn.jboss.org/repos/qa/richfaces/test-app-4.0.0.Final-JBoss-Tools... {quote} The file https://svn.jboss.org/repos/qa/richfaces/test-app-4.0.0.Final-JBoss-Tools... is correct now, because I altered it. But on default the common.xhtm contains tags like <head> and <body> without h: prefix. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RFPL-1285?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on RFPL-1285: -------------------------------------- {quote} As far as I can see, there is no quick fix for that, even if I find click on quickfix from context menu. {quote} This is a restriction of WTP. The only way to see quick fixes in WTP or JBoss Tools 3.2.0 is open it from context menu in Problems View. We fixed this restriction for our editor (which extends WTP's one) for JBoss Tools 3.3.0.M1. See https://issues.jboss.org/browse/JBIDE-8350 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira