[JBoss JIRA] (JBIDE-3170) Facets issues during creating JSF Projects.
by Zbyněk Červinka (Jira)
[ https://issues.redhat.com/browse/JBIDE-3170?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka closed JBIDE-3170.
----------------------------------
> Facets issues during creating JSF Projects.
> -------------------------------------------
>
> Key: JBIDE-3170
> URL: https://issues.redhat.com/browse/JBIDE-3170
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 3.0.0.cr1
> Environment: WindowsXP SP2
> JBoss Tools
> Version: 3.0.0.CR1
> Build id: JBossTools-3.0.0.CR1-N200811080256
> JDK 1.5_08
> Reporter: Aliaksey Nis
> Assignee: Aliaksey Nis
> Priority: Minor
> Attachments: FacetSelection.txt, JSFfacet.JPG
>
>
> Part 1.
> EXECUTE: New > Project > JBoss Tools > JSF > new JSF Project.
> EXECUTE: Input name, select JSF 1.01, Select KickStart w/o libs, press Next.
> EXECUTE: Uncheck target server checkbox, press Finish.
> ASSERT: JSF project successfully created.
> EXECUTE: Open web.xml.
> ASSERT: <servlet-mapping>
> <servlet-name>Faces Servlet</servlet-name>
> <url-pattern>*.jsf</url-pattern>
> Those strings presented in web.xml.
> EXECUTE: Right click on JSF project, select Properties, select Project Facets.
> FAILURE(?): JSF facet not enabled.
> EXECUTE: Enable JSF facet (1.1), press "future configuration needed" link.
> FAILURE(?): "URL mapping = *.seam" instead of "URL mapping = *.jsf". Screenshot attached. If this field not changed, and Ok(+Apply) button pressed - in web.xml url-pattern changed to *.seam.
> EXECUTE: Change field URL mapping to "*.jsf" value. Press Ok.
> FAILURE: Exception thrown in error log. If window closed via cross button - same exception thrown. Exception log attached.
> Part 2.
> EXECUTE: New > Project > Web > Dynamic Web project.
> EXECUTE: Input name, select configuration "Java server faces v1.1 project".
> ASSERT: Press modify button, check that JSF 1.1 checkbox - enabled.
> EXECUTE: Press next till JSF capabilities step.
> FAILURE: "URL mapping = *.seam" instead of "URL mapping = *.jsf".
> ASSERT: JSF project successfully created.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (JBIDE-5640) CSS stylesheets not considered when configured as a JSF 2 resource
by Zbyněk Červinka (Jira)
[ https://issues.redhat.com/browse/JBIDE-5640?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka closed JBIDE-5640.
----------------------------------
> CSS stylesheets not considered when configured as a JSF 2 resource
> ------------------------------------------------------------------
>
> Key: JBIDE-5640
> URL: https://issues.redhat.com/browse/JBIDE-5640
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 3.1.0.CR1
> Reporter: Juergen Zimmermann
> Assignee: Maxim Areshkau
> Priority: Major
> Labels: jsf2
> Fix For: 3.1.0.CR2
>
> Attachments: screenshot-with-unconsidered-css-file.jpg
>
>
> In JSF 2 a CSS stylesheet can be configured as a resource:
> <link rel="stylesheet" type="text/css" href="#{resource['css:hska.css']}"/>
> This means that the css file "hska.css" can be found in a subdirectory "css" of the directory "resources" (plural although the variable is just named "resource" !). The directory "resources" can be found either
> a) just below "WebContents" of the web project or
> b) in src/META-INF of the web project
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (JBIDE-6402) features must now depend on org.eclipse.jsf.feature as well as org.eclipse.jst.web_core.feature/org.eclipse.jst.web_ui.feature
by Zbyněk Červinka (Jira)
[ https://issues.redhat.com/browse/JBIDE-6402?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka closed JBIDE-6402.
----------------------------------
> features must now depend on org.eclipse.jsf.feature as well as org.eclipse.jst.web_core.feature/org.eclipse.jst.web_ui.feature
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-6402
> URL: https://issues.redhat.com/browse/JBIDE-6402
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 3.2.0.M1
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Priority: Major
>
> From David Williams on cross-projects-issues-dev(a)eclipse.org:
> It is far later than it should be, to be making this kind of change, so I am sending this notice to wtp-dev list and cross-project list to make sure it gets proper visibility.
> In WTP, the JEE and the JSF subprojects have regrouped a set of JSF bundles that used to be mingled in with the JEE bundles for packaging purposes, and pulled them out into their own, new JSF feature.
> This was required to allow more flexible packaging options and, more importantly, independent maintenance releases in the future. See bug 302896.
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=302896
> The implication is that anyone that has a feature that prereqs or installs
> *org.eclipse.jst.web_core.feature*, or
> *org.eclipse.jst.web_ui.feature*
> will now have to also prereq or install
> *org.eclipse.jsf.feature*
> to have the same, JSF functionality and bundles pulled in, that is.
> Similar for SDK counterparts; there is now an org.eclipse.jsf_sdk.feature.
> These new features are versioned as "3.2.0" to match the previous feature and highest bundle version.
> Apologies for the late change. Entirely my fault for not realizing the importance of this change earlier.
>
> I have, naturally, updated the webtools.build file and opened a bugzilla entry to update EPP Java EE package appropriately.
> See bug 314969
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=314969
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months