[JBoss JIRA] Created: (RF-8559) richfaces-demo - Drag Support - Argument Error: Parameter text is null
by Lukas Fryc (JIRA)
richfaces-demo - Drag Support - Argument Error: Parameter text is null
----------------------------------------------------------------------
Key: RF-8559
URL: https://jira.jboss.org/jira/browse/RF-8559
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JSF 2.0
Affects Versions: 3.3.3.Final
Environment: Internet Explorer 8
richfaces-demo-jsf2-3.3.3.Final-tomcat6.war
Apache Tomcat 6.0.24 (on Linux, IcedTea6 1.6.1)
Reporter: Lukas Fryc
Assignee: Lukas Fryc
Attachments: Error - Argument Error Parameter text is null.htm
I cannot reproduce it anymore, but I used following scenario, facelets debug page attached:
1. open richfaces-demo
2. open Drag Support
3. accidentaly move Sources to targets
4. sometimes happens that dragged source is frozen over wrong target (in not accepting state)
5. when conditions corresponds 4.,
- I dragged another item to its target (doesn't remember if accepting or declining type)
- and when rerendered after this action
- I can see attached facelets page
- when refreshed page, facelets page was still present
--
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
14 years, 8 months
[JBoss JIRA] Created: (RF-5041) ExtendedDataTable don't reRender with dynamic columns.
by Mikhail Vitenkov (JIRA)
ExtendedDataTable don't reRender with dynamic columns.
------------------------------------------------------
Key: RF-5041
URL: https://jira.jboss.org/jira/browse/RF-5041
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.3.0
Environment: IE6,7, FF3.0.3, Safari 3.1, Opera 9.62(seam 2.0.2.GA)
Reporter: Mikhail Vitenkov
Assignee: Nick Belaevski
#1. Add extendedDataTable to page:
<rich:extendedDataTable value="#{testBean.rows}" var="row">
<rich:columns value="#{testBean.columns}" var="column" index="ind">
<f:facet name="header">
<h:outputText value="#{column.name}" />
</f:facet>
<h:outputText value="#{row[ind]}" />
</rich:columns>
</rich:extendedDataTable>
<a:commandButton value="Add column" action="#{testBean.addAColumn}" reRender="form" />
#2. Define addAColumn method following way:
public void addAColumn(){
columns=Arrays.asList(new Column[]{new Column("Col1"),new Column("Col2"),new Column("Col3")});
rows=Arrays.asList(Arrays.asList(new String[]{"a","b","c"}),Arrays.asList(new String[]{"d","e","f"}));
}
#3. Navigate to page, contained tested component & try to add one row.
Following exception occurs:
Error Rendering View[/CustomizePage/CustomizePage.xhtml]
java.lang.NullPointerException
at org.richfaces.component.ColumnsSizeState.getColumnSize(ExtendedDataTableState.java:299)
at org.richfaces.component.ExtendedDataTableState.getColumnSize(ExtendedDataTableState.java:159)
at org.richfaces.component.UIExtendedDataTable.getColumnSize(UIExtendedDataTable.java:183)
at org.richfaces.renderkit.AbstractExtendedTableRenderer.encodeColumns(AbstractExtendedTableRenderer.java:130)
at org.richfaces.renderkit.html.ExtendedDataTableRenderer.doEncodeBegin(ExtendedDataTableRenderer.java:281)
at org.richfaces.renderkit.html.ExtendedDataTableRenderer.doEncodeBegin(ExtendedDataTableRenderer.java:216)
at org.ajax4jsf.renderkit.RendererBase.encodeBegin(RendererBase.java:101)
at org.richfaces.renderkit.AbstractExtendedTableRenderer.encodeBegin(AbstractExtendedTableRenderer.java:1346)
at javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.java:788)
at javax.faces.component.UIData.encodeBegin(UIData.java:879)
at org.ajax4jsf.component.UIDataAdaptor.encodeBegin(UIDataAdaptor.java:1220)
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:884)
at javax.faces.render.Renderer.encodeChildren(Renderer.java:137)
at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:812)
at org.ajax4jsf.renderkit.RendererBase.renderChild(RendererBase.java:282)
at org.ajax4jsf.renderkit.AjaxChildrenRenderer.encodeAjaxComponent(AjaxChildrenRenderer.java:124)
at org.ajax4jsf.renderkit.AjaxChildrenRenderer.encodeAjaxChildren(AjaxChildrenRenderer.java:67)
at org.ajax4jsf.renderkit.AjaxChildrenRenderer.encodeAjaxComponent(AjaxChildrenRenderer.java:115)
at org.ajax4jsf.renderkit.AjaxContainerRenderer.encodeAjax(AjaxContainerRenderer.java:123)
at org.ajax4jsf.component.AjaxViewRoot.encodeAjax(AjaxViewRoot.java:677)
at org.ajax4jsf.component.AjaxViewRoot.encodeChildren(AjaxViewRoot.java:548)
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:886)
at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:592)
at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:100)
at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:197)
at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:106)
at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251)
at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:144)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:245)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:85)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:565)
at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:60)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:68)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:307)
at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:423)
at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:550)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
at java.lang.Thread.run(Unknown Source)
--
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
14 years, 8 months
[JBoss JIRA] Closed: (RF-8436) seam-gen should not use resources:// for things that are in web/view content
by Lukas Fryc (JIRA)
[ https://jira.jboss.org/jira/browse/RF-8436?page=com.atlassian.jira.plugin... ]
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: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months
[JBoss JIRA] Commented: (RF-8436) seam-gen should not use resources:// for things that are in web/view content
by Lukas Fryc (JIRA)
[ https://jira.jboss.org/jira/browse/RF-8436?page=com.atlassian.jira.plugin... ]
Lukas Fryc commented on RF-8436:
--------------------------------
Steps to reproduce:
JBDS 3.0.0.GA
JBoss AS 5.1..0.GA
Seam 2.2.0.GA
1. generate new Seam Web Project
2. deploy using JBDS
3. verify that /${ROOT}/home.seam have link refering to xcss file:
3a. (with RF 3.3.1.GA - included by default) direct reference (e.g.: <link class="user" href="/rf8436/stylesheet/theme.xcss" rel="stylesheet" type="text/css" />)
3b. (with RF 3.3.3.Final - replace libs in WEB-INF/lib) reference to preprocess (e.g.: <link class="user" href="/rf8436/a4j/s/3_3_3.Final/stylesheet/theme.xcss/DATB/eAF7sqpgb-jyGdIAFrMEaw__" rel="stylesheet" type="text/css" />)
> 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: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months