[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4384) Seam/Hibernate filter enabled --> ClassCastException
by bernd farka (JIRA)
Seam/Hibernate filter enabled --> ClassCastException
----------------------------------------------------
Key: JBSEAM-4384
URL: https://jira.jboss.org/jira/browse/JBSEAM-4384
Project: Seam
Issue Type: Bug
Affects Versions: 2.2.0.GA
Reporter: bernd farka
When i want die enabled a filter in this way
<persistence:filter name="userFilter" enabled="true">
<persistence:name>userFilter</persistence:name>
<persistence:parameters>
<key>personToken</key>
<value>#{identity.principal.name}</value>
</persistence:parameters>
</persistence:filter>
It comes to a ClassCastException in org.jboss.seam.persistence.Filter : public boolean isFilterEnabled() at line 80.
If the enabled flag is turned to false the same Exception happens, if it filter is changed to this way it works fine
<persistence:filter name="userFilter" >
<persistence:name>userFilter</persistence:name>
<persistence:parameters>
<key>personToken</key>
<value>#{identity.principal.name}</value>
</persistence:parameters>
</persistence:filter>
wbr
Bernd Farka
--
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
15 years, 4 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4383) Implement supporting infrastructure for HTTP optimization
by Christian Bauer (JIRA)
Implement supporting infrastructure for HTTP optimization
---------------------------------------------------------
Key: JBSEAM-4383
URL: https://jira.jboss.org/jira/browse/JBSEAM-4383
Project: Seam
Issue Type: Feature Request
Components: Core
Reporter: Christian Bauer
Assignee: Christian Bauer
We need the following to allow Seam users to optimize their application's HTTP communication:
- A new method called selectOutputStream() in AbstractResource that is able to GZIP content if supported by the browser, transparently to the actual AbstractResource implementation. Although this is the job of Tomcat, it sometimes for unknown reasons does not compress a resource representation.
- A new CacheControlFilter that provides cache-control headers, configurable in components.xml:
<web:cache-control-filter name="resourcesCacheControlFilter" regex-url-pattern=".*(\.gif|\.png|\.jpg|\.jpeg|\.css|\.js)" value="max-age=86400"/> <!-- 1 day -->
- A new alternative to AbstractResource called ConditionalAbstractResource which provides the sendConditional() method that can, using entity tags and last modified timestamps, return a 304 Not Modified instead of the actual resource representation. This is used by browsers after an item in the local cache expires, Seam users can subclass ConditionalAbstractResource to define the entity tag and last modified validation conditions.
--
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
15 years, 4 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4377) seam is not logging exceptions on failures of outjection
by deanhiller (JIRA)
seam is not logging exceptions on failures of outjection
--------------------------------------------------------
Key: JBSEAM-4377
URL: https://jira.jboss.org/jira/browse/JBSEAM-4377
Project: Seam
Issue Type: Bug
Components: Exception Handling
Affects Versions: 2.1.0.GA
Environment: jboss 5.0.1 and tomcat6.0.16 as well and seam version above
Reporter: deanhiller
If @Out is required and is not there, seam correctly fails and logs nothing. In our QA environment, debug is false of course, so I can't see what went wrong on the server with a nice stack trace. Instead it is swallowed. When I run in debug mode, the correct seam debug comes up, but it is still not logged in the logs like all the other exceptions. This needs to be logged just in case I can't reproduce it in development so that I have some data on what happened instead of having no data at all on the exception that occurred in test or production. Please add a simple log to log these exceptions!!!!
--
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
15 years, 4 months