[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-4500) xcss templates should be copied to the classpath on deploy

[Alexander Smirnov (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-4500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12509917#action_12509917 ] 

Alexander Smirnov commented on JBIDE-4500:
------------------------------------------

RichFaces uses these special URI's because of its skins dynamic nature. Most of stylesheets and images are generated "on the fly" so tools have to get generated content by some way. We can generate static files at development time so they could be used instead of dynamic ones in editor, but that will disable ability to get proper page content for different skin.
Another way, that has already been discussed couple of times is using embedded container, maybe simlified one that we are using for test, to run page and provide actual HTML code to editor. In this case, visual editor can show actual page even for third-party components, but Denis said that it would be hard to edit such content because editor has to make backward transformation, from HTML to component and its attributes.

> xcss templates should be copied to the classpath on deploy
> ----------------------------------------------------------
>
>                 Key: JBIDE-4500
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-4500
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: UpStream
>    Affects Versions: 3.0.1.GA
>         Environment: winxp x86, jdk6, jboss5
>            Reporter: Jacques Lemire
>            Assignee: Jay Balunas
>            Priority: Critical
>             Fix For: 3.1.0.CR2
>
>
> 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: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira