[JBoss JIRA] Created: (JBPORTAL-1094) ClassCastException when casting SubSession to List in PortalSessionSynchronizationInterceptor
by Poul Bildsoee Moeller (JIRA)
ClassCastException when casting SubSession to List in PortalSessionSynchronizationInterceptor
---------------------------------------------------------------------------------------------
Key: JBPORTAL-1094
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1094
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal Portlet
Affects Versions: 2.4 Final
Environment: Portal Clustered using both Portal-ha-2.4.1CR1 and 2.4.0-ha running on JBoss AS 4.0.4
Reporter: Poul Bildsoee Moeller
Assigned To: Julien Viet
Priority: Minor
In org.jboss.portal.portlet.aspects.portlet.PortalSessionSynchronizationInterceptor the following code is executed (code partially inserted):
HttpSession session = req.getSession(false);
if (session != null)
{
ss = (SubSession)session.getAttribute(key);
}
//
try
{
// Set the sub session for the portlet synchronization
if (ss != null && ss.isActivated())
{
invocation.setAttribute("subsession", ss);
}
//
invocation.invokeNext();
}
finally
{
List modifications = (List)invocation.getAttribute("subsession");
The code sets the SubSession as an attribute on invocation and then later tries to fetch this again and at the same time cast to List. This doesn't work since SubSession isn't a List. I am not sure what is meant to happen so I cannot really fix the problem myself.
--
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
19 years, 5 months
[JBoss JIRA] Created: (JBXB-89) JBossXB automatically unzips gzipped content when decoding base64 data.
by Darran Lofthouse (JIRA)
JBossXB automatically unzips gzipped content when decoding base64 data.
-----------------------------------------------------------------------
Key: JBXB-89
URL: http://jira.jboss.com/jira/browse/JBXB-89
Project: JBoss XML Binding (JBossXB)
Issue Type: Bug
Affects Versions: JBossXB-1.0.0.CR7
Reporter: Darran Lofthouse
Fix For: JBossXB-1.0
JBossXB automatically unzips gzipped content when decoding base64 data.
The reason why it is automatically unzipped is becuase the method unmarshalBase64 in org.jboss.xb.binding.SimpleTypeBindings is calling the method decode in org.jboss.util.Base64, this decode method after converting from Base64 detects that it is gzipped so unzippes it. If we do not need to unzip the data we could call the decode method that takes the byte array instead of a String as this does not perform any unzipping.
--
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
19 years, 5 months
[JBoss JIRA] Created: (JBREM-640) Implement an asynchronous method for handling callbacks.
by Ron Sigal (JIRA)
Implement an asynchronous method for handling callbacks.
--------------------------------------------------------
Key: JBREM-640
URL: http://jira.jboss.com/jira/browse/JBREM-640
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 2.2.0.Beta1 (Bluto)
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.2.0.Beta1 (Bluto)
Tim Fox:
Currently, it's my understanding that push callbacks (using socket transport anyway) are synchronous, i.e. the server side thread that executes the callback blocks until the callback has been delivered to the client side and returned.
Is it currrently possible to execute asynch push callbacks? I.e. the thread that calls the callback returns immediately once it has registered the callback with remoting. And it is then delivered on a different thread?
Ideally executing using some kind of executor (e.g. PooledExecutor) with a bounded queue size which blocks when it is full would be ideal.
--
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
19 years, 5 months