]
Lukas Fryc closed RF-8436.
--------------------------
Reproduced in 3.3.3.CR1, verified in 3.3.3.GA.
seam-gen should not use resources:// for things that are in web/view
content
----------------------------------------------------------------------------
Key: RF-8436
URL:
https://jira.jboss.org/jira/browse/RF-8436
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: CDK, core, tools
Environment: winxp x86, jdk6, jboss5
Reporter: Jacques Lemire
Assignee: Alexander Smirnov
Priority: Blocker
Fix For: 3.3.3.Final
seam-gen templates are using resource:// for things that are not on the classpath
(currently build.xml hacks around this by duplicating the .xcss files in the war)
Original description:
In projects generated through "File" -> "New" -> "Seam web
project", the facelets template "layout/template.xhtml" contains the
following component in the "head" section:
layout/template.xhtml:
<a:loadStyle src="resource:///stylesheet/theme.xcss"/>
This component, from a4j should transform the "richfaces templatable css"
(xcss) file into a real CSS file and render as a <link> tag containing an a4j
resource url. In projects created from the command-line seam-gen script, the output is as
expected:
<link class='user' rel='stylesheet' type='text/css'
href='/testxcss/a4j/s/3_2_2.SR1stylesheet/theme.xcss/DATB/eAFrvajdHLp8hjQAEgwDtA__'
/>
However, using jboss tools, I get:
<link class='user' rel='stylesheet' type='text/css'
href='/SeamThemeTest/stylesheet/theme.xcss' />
This version does not work, however, as the xcss file is returned to the browser as is.
By looking at the differences between the seam-gen project and the jbosstools project, i
noticed the following section of the build.xml ant file generated by seam-gen:
<copy todir="${war.dir}/WEB-INF/classes">
<fileset dir="${basedir}/resources">
<include name="**/*.xcss"/>
</fileset>
<!-- move XCSS into classpath for now
loading from web context only works in JBoss AS 4 -->
<fileset dir="${basedir}/view">
<include name="**/*.xcss"/>
</fileset>
</copy>
This step is not done by jbosstools (3.1.0), and indeed, by doing a quick web search, I
fell on the following jira:
https://jira.jboss.org/jira/browse/JBAS-6034, which states
that:
> [...] that would work in 4.2.x but not in jboss5 where the root of the war is no
longer a part of the war's classpath (and never should have been!)
Please fix it as soon as possible, as this problem affects any generated site and is
pretty difficult to debug. On the other hand, it should be very easy to fix.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: