[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3742) pages.xsd cannot use static navigation
by Gonzalez Adrian (JIRA)
pages.xsd cannot use static navigation
--------------------------------------
Key: JBSEAM-3742
URL: https://jira.jboss.org/jira/browse/JBSEAM-3742
Project: Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.1.0.SP1
Reporter: Gonzalez Adrian
pages-2.1.xsd is too restrictive, I cannot write anymore :
<navigation from-action="goBack">
>From pages.xsd definition, 'from-action' value must always be an El expression (so called 'dynamic navigation').
This shouldn't be the case, web should be able to use static navigation.
Here's the pages-2.1.xsd showing the restriction :
<xs:simpleType name="view-id">
<xs:restriction base="xs:string">
<xs:pattern value="(/.*)|\*"/>
</xs:restriction>
</xs:simpleType>
<xs:attributeGroup name="attlist.navigation">
<xs:attribute name="from-action" type="pages:method-expression" />
<xs:attribute name="evaluate" type="pages:method-expression" />
</xs:attributeGroup>
--
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, 11 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3729) Recognize HotDeployFilter as a configurable filter in web.xsd
by Dan Allen (JIRA)
Recognize HotDeployFilter as a configurable filter in web.xsd
-------------------------------------------------------------
Key: JBSEAM-3729
URL: https://jira.jboss.org/jira/browse/JBSEAM-3729
Project: Seam
Issue Type: Feature Request
Components: Hot Deploy
Affects Versions: 2.1.0.SP1
Reporter: Dan Allen
Fix For: 2.1.1.CR2
It's absolutely critical that the HotDeployFilter only be applied to JSF requests or else the scanning that it does occurs for every related requested by the page. However, currently none of the XML schemas for the component descriptor recognize this filter as a configurable element. Here is how it has to be configured now:
<component name="org.jboss.seam.debug.hotDeployFilter">
<property name="urlPattern">*.seam</property>
</component>
I would like to do one of two things.
#1
Change the component name from org.jboss.seam.debug.hotDeployFilter to org.jboss.seam.web.hotDeployFilter (but still keep it in jboss-seam-debug.jar), then add the hot-deploy-filter element to web.xsd. We would get this:
<web:hot-deploy-filter url-pattern="*.seam"/>
We could even consider moving this filter into jboss-seam.jar because honestly it is so lightweight and really has everything to do with the core and is already controlled by the debug mode flag in Seam.
#2
Keep the component name as is and introduce a new namespace http://jboss.org/products/seam/debug and a corresponding package-info.java and debug.xsd. Then add the hot-deploy-filter to debug.xsd. We would get this:
<debug:hot-deploy-filter url-pattern="*.seam"/>
I really hate solution #2. The only redeeming quality is that it doesn't break applications that might rely on this component name. But then again, it would only affect debug mode, not production apps.
--
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, 11 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3728) not clearing EntityManager in ManagedPersistenceContext#sessionWillPassivate breaks session replication
by Dan Allen (JIRA)
not clearing EntityManager in ManagedPersistenceContext#sessionWillPassivate breaks session replication
-------------------------------------------------------------------------------------------------------
Key: JBSEAM-3728
URL: https://jira.jboss.org/jira/browse/JBSEAM-3728
Project: Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.1.0.SP1
Reporter: Dan Allen
Fix For: 2.1.1.CR2
Commit 8372 broke the clustering because EntityManager is not being cleared before session passivation. The EntityManager cannot be serialized and therefore to leave it in the conversation context (and hence the session context) prevents the HTTP session from being restored properly. Two ways to fix is either set the EntityManager it to null in the ManagedPersistenceContext#sessionWillPassivate method (the old behavior, which gives us a chance to clean things up) or mark the field as transient. Making the field transient solves the problem that commit 8372 was attempting to fix, which was that the entities were being reloaded from the database on each request in a clustered environment. The problem with using transient is that we don't get an opportunity to formally close the EntityManager (but then again, it might be hard to tell when the session being used jumps a node in the cluster, which is the only time you want to destroy the EntityManager).
--
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, 11 months