[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1293) Page parameters not working
by Chris Rudd (JIRA)
Page parameters not working
---------------------------
Key: JBSEAM-1293
URL: http://jira.jboss.com/jira/browse/JBSEAM-1293
Project: JBoss Seam
Issue Type: Bug
Affects Versions: 1.2.1.GA
Reporter: Chris Rudd
Im attempting to use the Page parameter feature detailed in section 5.1.1.1 of the documentation.
<pages>
<page view-id="/edit.xhtml">
<param name="id" value="#{editor.id}"/>
</page>
</pages>
based on my understanding of the functiuonality if i go the url /edit.xhtml?id=foobar then editor.id should be set to 'foobar'.
This is not occuring. After tracing the code it seems like this is where the magic should happen:
AbstractSeamPhaseListener.java : 70
//apply page parameters to the model
if ( facesContext.getRenderResponse() )
{
Pages.instance().applyRequestParameterValues(facesContext);
}
else
{
Pages.instance().applyViewRootValues(facesContext);
}
Im using myfaces 1.1.4 with server side view state. What appears to be happening is that myfaces will restore the saved view state (im not sure it should be, as its a GET request). When this happends facesContext.renderResponse is never called.
Thus when it gets to the above code, the page parameters are restored from the wrong location.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 5 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1131) Example web.xml is incomplete
by Christian Bauer (JIRA)
Example web.xml is incomplete
-----------------------------
Key: JBSEAM-1131
URL: http://jira.jboss.com/jira/browse/JBSEAM-1131
Project: JBoss Seam
Issue Type: Bug
Components: Tools
Reporter: Christian Bauer
I was running into this when using an ajax4jsf tag:
SEVERE: Error Rendering View[/docDisplay.xhtml]
javax.faces.FacesException: Resources framework is not initialised, check web.xml for Filter configuration
at org.ajax4jsf.framework.resource.ResourceBuilderImpl.getWebXml(ResourceBuilderImpl.java:107)
at org.ajax4jsf.framework.resource.ResourceBuilderImpl.getUri(ResourceBuilderImpl.java:309)
at org.ajax4jsf.framework.resource.InternetResourceBase.getUri(InternetResourceBase.java:211)
at org.ajax4jsf.framework.resource.BaseResourceRenderer.encodeBegin(BaseResourceRenderer.java:62)
at org.ajax4jsf.framework.resource.OneTimeRenderer.encodeBegin(OneTimeRenderer.java:48)
at org.ajax4jsf.framework.resource.BaseResourceRenderer.encode(BaseResourceRenderer.java:45)
at org.ajax4jsf.framework.resource.InternetResourceBase.encode(InternetResourceBase.java:306)
at org.ajax4jsf.framework.resource.ClientScript.encode(ClientScript.java:143)
at org.ajax4jsf.framework.renderer.HeaderResourcesRendererBase.encodeResourcesArray(HeaderResourcesRendererBase.java:131)
at org.ajax4jsf.framework.renderer.HeaderResourcesRendererBase.preEncodeBegin(HeaderResourcesRendererBase.java:117)
at org.ajax4jsf.framework.renderer.RendererBase.encodeBegin(RendererBase.java:98)
at javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.java:512)
at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:242)
at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:249)
at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:249)
at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:573)
at org.ajax4jsf.framework.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108)
at org.ajax4jsf.framework.ajax.AjaxViewHandler.renderView(AjaxViewHandler.java:229)
at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:384)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:138)
It only happened right after redeployment, and if the first page I called (with an ajax4jsf tag on it) was behind my rewrite filter, last in web.xml:
<filter>
<filter-name>UrlRewriteFilter</filter-name>
<filter-class>org.tuckey.web.filters.urlrewrite.UrlRewriteFilter</filter-class>
<init-param>
<param-name>logLevel</param-name>
<param-value>WARN</param-value>
</init-param>
<init-param>
<param-name>statusEnabled</param-name>
<param-value>false</param-value>
</init-param>
</filter>
<filter-mapping>
<filter-name>UrlRewriteFilter</filter-name>
<url-pattern>/*</url-pattern>
</filter-mapping>
Note that this rewrites internally somehow, not with a redirect. If I called, right after deployment, a page with a not rewritten URL and an ajax4jsf tag on it, it would work fine. Interesting enough but after it would work once, even pages that had rewritten URLs worked fine. So there is some initialization issue hidden in this somewhere.
After reading this http://jboss.com/index.html?module=bb&op=viewtopic&t=103561 I started playing with random web.xml settings. Take a seam-gen WAR deployment web.xml and make the following modifications:
<filter-mapping>
<filter-name>ajax4jsf</filter-name>
<url-pattern>*.seam</url-pattern>
<dispatcher>REQUEST</dispatcher>
<dispatcher>FORWARD</dispatcher>
<dispatcher>INCLUDE</dispatcher>
</filter-mapping>
<filter-mapping>
<filter-name>Seam Filter</filter-name>
<url-pattern>*.seam</url-pattern>
</filter-mapping>
This seems to work now. I have no idea what happens.
Put this on the Java EE 6.0 list: web.xml must be replaced with something that makes sense. Or we need to find a proprietary way to configure a stack of a dozen filters with explicit URL pattern/precedence matching. Maybe we should move this into a Seam config file and initialize the web container programmatically (if that is possible).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 6 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1190) Disabling install of core components no longer works
by Mike Quilleash (JIRA)
Disabling install of core components no longer works
----------------------------------------------------
Key: JBSEAM-1190
URL: http://jira.jboss.com/jira/browse/JBSEAM-1190
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 1.2.1.GA
Environment: Any
Reporter: Mike Quilleash
Upgrading from Seam 1.1.6 to 1.2.1 seems to have broken the ability to do this...
<component class="org.jboss.seam.web.ExceptionFilter" installed="false"/>
In my WEB-INF/components.xml. The logic in the dependency manager scans both component descriptors, ignores the first as it is set to not install and then installs the second (default) one as normal. I believe the precedence of two components is not being honoured with regard to the installed flag.
Possible in
private boolean tryToInstall(String key) {
it should stop looping immediatly if it finds a non-installed component rather than skipping that descriptor and continuing to the next loop.
This is a rather major issue for me as the exception filter is causing problems elsewhere (see bug 1188) and I can't seem to find out how to turn it off!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 6 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1519) generate-entities should populate and deliver hibernate-console.cfg.xml
by Dan Allen (JIRA)
generate-entities should populate and deliver hibernate-console.cfg.xml
-----------------------------------------------------------------------
Key: JBSEAM-1519
URL: http://jira.jboss.com/jira/browse/JBSEAM-1519
Project: JBoss Seam
Issue Type: Patch
Components: Tools
Affects Versions: 1.3.0.ALPHA
Environment: seam CVS HEAD
Reporter: Dan Allen
Priority: Minor
When seam-gen executes the new-project command, it puts a hibernate-console.properties file in place for the Hibernate Console Eclipse plugin. This works fine for a blank project. However, after generate-entities executes, the Hibernate Console configuration cannot see the new entities. For that, a Hibernate Configuration (cfg.xml) file is required.
I have created a patch that uses <hbmtemplate /> to create a hibernate-console.cfg.xml file with each of the entities created by generate-entities. The only downside is that it will clobber an existing hibernate-console.cfg.xml file. However, we could either enhance the build to be smart about this, or we just say what the hell, this is a prototype tool so expect some clobbering.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 6 months