[JBoss JIRA] Created: (GTNCOMMON-14) Update support for Mime Types
by Matt Wringe (JIRA)
Update support for Mime Types
-----------------------------
Key: GTNCOMMON-14
URL: https://jira.jboss.org/browse/GTNCOMMON-14
Project: GateIn Common
Issue Type: Feature Request
Reporter: Matt Wringe
Some of the mime type handling is done in the common module (see the org.gatein.common.net.media package). In the GateIn portal and WSRP module (and probably in other modules as well) mime types are also partially handled.
What we need is to handle more of the mime types in the common module or use a third party mime type library.
What we would need done is:
1) determine if we are dealing with text content or binary content.
-We cannot assume that if the mime type is not 'text' then we are dealing with binary content. 'application/javascript' or 'application/emcascript' should be considered as text. We need to create a list to determine this (and include the non standard x-* types)
-We also cannot determine if we are dealing with text or binary content based on if we receive characters or bytes back. The text content can be returned as a byte array.
2) properly determine the encoding of text content. The encoding type can be determined by looking at the first few bytes of data (this is optional), we are currently not looking into bytes to determine the encoding.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] Created: (GTNPORTAL-1701) FilterDefinition should match the patterns properly
by Khoi Nguyen (JIRA)
FilterDefinition should match the patterns properly
---------------------------------------------------
Key: GTNPORTAL-1701
URL: https://jira.jboss.org/browse/GTNPORTAL-1701
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.1.0-GA
Reporter: Khoi Nguyen
Assignee: Khoi Nguyen
In ExtensibleFilter, we only execute the filters which match to path of request URI. So we should match to path regardless portal container name.
For example:
In sample extension, we had SampleFilter with pattern was /.*. If we change pattern to /simpleFilter, SimpleFilter cannot be executed because the path URI is /portal/simpleFilter (with portal container name is 'portal'). Actually, we want do filter to SimpleFilter when in the path has /simpleFilter regardless portal container name
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] Created: (GTNPORTAL-1705) wrong httpsession when instaling LocalizationFilter
by ahmed zaoui (JIRA)
wrong httpsession when instaling LocalizationFilter
----------------------------------------------------
Key: GTNPORTAL-1705
URL: https://jira.jboss.org/browse/GTNPORTAL-1705
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: WebUI
Reporter: ahmed zaoui
Util.getPortalRequestContext().getRequest().getSession().getAttribute
return null attribute after installing LocalizationFilter
ApplicationDispatcher doesn't wrap the ServletFacade , it wrap the HttpRequestWrapper (RequestFacade has already
wrapped by LocalizationFilter so the getSession() will return the wrong session with null attribute
because HttpRequestWrapper is instanceof ServletRequestWrapper, and inject a
different request object into it via inherited setRequest() method
and making it wrap a completely different request.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month