[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1296) Add <propagation type="?"/> as a child to <rule> or <redirect/> / <render/> in pages.xml
by Chris Rudd (JIRA)
Add <propagation type="?"/> as a child to <rule> or <redirect/> / <render/> in pages.xml
----------------------------------------------------------------------------------------
Key: JBSEAM-1296
URL: http://jira.jboss.com/jira/browse/JBSEAM-1296
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 1.2.1.GA, 1.2.0.GA
Reporter: Chris Rudd
While you can add a the propagation via a parameter its a bit verbose and cluttered (due to the value binding string literal)
<page view-id="/editDocument.xhtml">
<navigation from-action="#{documentEditor.update}">
<rule if="#{documentEditor.errors.empty}">
<end-conversation/>
<redirect view-id="/viewDocument.xhtml">
<param name="conversationPropagation" value="#{'none'}"/>
</redirect>
</rule>
</navigation>
</page>
Adding a <propagation type="?"/> would be much cleaer.
<page view-id="/editDocument.xhtml">
<navigation>
<rule if-outcome="done">
<end-conversation/>
<redirect view-id="/viewDocument.xhtml">
<propagation type="none"/>
</redirect>
</rule>
</navigation>
</page>
Side note :
The reason for needing to control the propagation in the circumstance above is so that the target view (/viewDocument.xhtml) can start with a new clean conversation. The redirect mechanism delays the end of the conversation untill it gets to the redirected to view, but I dont want that conv to be used. The before-redirect attribute doesnt work in this case as the redirect url needs to include data from the existing conversation (page parameters). I use the same scenario in other places via s:link/s:button but I cannot do this here as its dependent on the outcome not what link/button I pressed
--
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
16 years, 7 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1530) Seam-gen: @Length in char(1) property
by Luiz Augusto Ruiz (JIRA)
Seam-gen: @Length in char(1) property
-------------------------------------
Key: JBSEAM-1530
URL: http://jira.jboss.com/jira/browse/JBSEAM-1530
Project: JBoss Seam
Issue Type: Bug
Components: Tools
Affects Versions: 1.3.0.ALPHA
Reporter: Luiz Augusto Ruiz
Seam-gen put a @Length Hibernate validator in char property. When a field of a table is CHAR(1) Hibernate generates a char property and seam-gen put a @Length(size=1).
This can be fixed updating the template pojo/GetPropertyAnnotation.ftl:
<#include "Ejb3PropertyGetAnnotation.ftl"/>
<#if !property.optional>
@${pojo.importType("org.hibernate.validator.NotNull")}
</#if>
<#if property.columnSpan==1>
<#assign column = property.getColumnIterator().next()/>
<#if !c2h.isManyToOne(property) && !c2h.isTemporalValue(property) && column.length!=255 && column.length!=1>
@${pojo.importType("org.hibernate.validator.Length")}(max=${column.length?c})
</#if>
</#if>
" && column.length!=1" fix the bug.
--
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
16 years, 7 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2158) Can't inject a org.hibernate.classic.Session
by Clint Popetz (JIRA)
Can't inject a org.hibernate.classic.Session
--------------------------------------------
Key: JBSEAM-2158
URL: http://jira.jboss.com/jira/browse/JBSEAM-2158
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 2.0.0.CR3
Reporter: Clint Popetz
If one does
import org.hibernate.classic.Session;
@In Session session;
the injection throws an IllegalArgumentException, because HibernateSessionProxy doesn't implement the classic Session interface. It seems harmless to do this, and would allow for easier migration of large source bases from loyal hibernate early adoptees that are now transitioning to the next-big-thing.
If making HibernateSessionProxy implement the classic interface would be acceptable, please make note of it here and I'll create a patch to that effect.
--
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
16 years, 7 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2427) Email rendering from async method/event fails to find web resources
by Allon Rauer (JIRA)
Email rendering from async method/event fails to find web resources
-------------------------------------------------------------------
Key: JBSEAM-2427
URL: http://jira.jboss.com/jira/browse/JBSEAM-2427
Project: JBoss Seam
Issue Type: Bug
Affects Versions: 2.0.0.GA
Reporter: Allon Rauer
Priority: Minor
Our system sometimes renders emails (system status, etc.) triggered by a periodic async event.
In this context, the email renderer cannot find the xhtml email templates that reside in the web resources directory.
Solution: in org.jboss.seam.ui.facelet.FaceletsRenderer
modify this block (to propagate the servlet context)....
from:
// If a FacesContext isn't available, set one up
if (FacesContext.getCurrentInstance() == null)
{
MockFacesContext mockFacesContext = new MockFacesContext(new MockExternalContext())
.setCurrent();
mockFacesContext.createViewRoot();
}
to:
// If a FacesContext isn't available, set one up
if (FacesContext.getCurrentInstance() == null)
{
MockFacesContext mockFacesContext = new MockFacesContext(new MockExternalContext(ServletLifecycle.getServletContext()))
.setCurrent();
mockFacesContext.createViewRoot();
}
--
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
16 years, 7 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-715) Allow multiple pages.xml files
by Stephan Bublava (JIRA)
Allow multiple pages.xml files
------------------------------
Key: JBSEAM-715
URL: http://jira.jboss.com/jira/browse/JBSEAM-715
Project: JBoss Seam
Issue Type: Feature Request
Components: JSF
Affects Versions: 1.1.1.GA
Reporter: Stephan Bublava
Currently it's possible to use one global pages.xml file or one file per page. I believe that both options are not well-suited for large applications.
Consider an application like:
/catalog/foo.xhtml
/bar.xhtml
/...
/basket/foo.xhtml
/bar.xhtml
/...
/admin/foo.xhtml
/bar.xhtml
/...
In this case using a global file would be too convoluted, but at the same time one file per page is too fine grained.
It would be great to allow one file per directory ("module"), either using a similar naming convention to page.xml or by adding an "import" tag to pages.xml.
--
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
16 years, 8 months