[JBoss JIRA] Created: (JBSEAM-4576) Upgrade Javassist to new version - current version has memory leaks
by Marek Novotny (JIRA)
Upgrade Javassist to new version - current version has memory leaks
-------------------------------------------------------------------
Key: JBSEAM-4576
URL: https://jira.jboss.org/jira/browse/JBSEAM-4576
Project: Seam
Issue Type: Task
Components: Core
Affects Versions: 2.2.0.GA, 2.2.0.CR1
Reporter: Marek Novotny
Assignee: Marek Novotny
Fix For: 2.2.1.CR2
The problem is caused by the current javassist usage pattern of calling ProxyFactory.createClass().newInstance() which currently (due to the broken cache), always creates a new class for the proxy. And once this class gets classloaded, you cannot easily get rid of it from the ClassLoaders class map.
There were also a few problems with deserialization, mainly because it did drop the assigned MethodHandler and used the DefaultMethodHandler instead.
Storing a static reference cause a problem for garbage collection, because the MethodHandler set directly into the ProxyFactory can never get freed.
Patches from Mark Struberg is available at http://github.com/struberg/javassist
--
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, 2 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4204) Hot redeploy is broken w/ JBoss AS 5
by Fred Bricon (JIRA)
Hot redeploy is broken w/ JBoss AS 5
------------------------------------
Key: JBSEAM-4204
URL: https://jira.jboss.org/jira/browse/JBSEAM-4204
Project: Seam
Issue Type: Bug
Components: Hot Deploy
Affects Versions: 2.1.2.CR2, 2.1.1.GA, 2.0.2.SP1
Environment: Vista, Eclipse Ganymede 3.4.2, JBoss Tools 3.0.1.GA, JBoss 5.0.1.GA
Reporter: Fred Bricon
Hi
It seems hot deployement doesn't work on JBoss 5.0.1.GA : when editing (and saving) xhtml files, JBoss Tools correctly publish the files to the JBoss AS deploy directory,
but changes are not picked up.
I tested projects created from the JBoss Tools wizards :
- booking (2.0.2.SP1 from the examples menu)
- simple 2.0.2.SP1 project
- simple 2.1.1.GA project
- simple 2.1.2.CR2 project
A simple seam-less dynamic web project, is correctly hot redeployed via JBoss Tools.
[Others|http://seamframework.org/Community/HotDeployAndJBoss5] have experienced this problem. I couldn't say if it's a Seam or an AS5 issue for sure, but I vote for the former.
regards,
Fred Bricon
--
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, 2 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4284) Wrong pageflow name in case of nested conversation
by Vesa Hiltunen (JIRA)
Wrong pageflow name in case of nested conversation
--------------------------------------------------
Key: JBSEAM-4284
URL: https://jira.jboss.org/jira/browse/JBSEAM-4284
Project: Seam
Issue Type: Bug
Affects Versions: 2.1.2.GA
Reporter: Vesa Hiltunen
I tried to start nested conversation with new pageflow as follows:
<s:link value="DoIt" action="/pages/myPage.xhtml">
<s:conversationPropagation type="nested" pageflow="myPageflowName" />
</s:link>
Seam did not find pageflow because it is looking for pageflow named as: d.myPageflowName
Request parameter was: conversationPropagation=nested.myPageflowName
It looks like method getPropagationFromRequestParameter(Map parameters) in org.jboss.seam.core.ConversationPropagation contains a bug. Method assumes that string "nested." was "nest."
Current code:
else if (value.startsWith("nest"))
{
propagationType = PropagationType.NEST;
if ( value.length()>5 )
{
pageflow = value.substring(5);
}
}
One way to fix the code:
else if (value.startsWith("nest"))
{
propagationType = PropagationType.NEST;
if ( value.length()>7 )
{
pageflow = value.substring(7);
}
}
--
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, 2 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3883) URL rewriting broken for view-id of redirects in exceptions
by Stephen Friedrich (JIRA)
URL rewriting broken for view-id of redirects in exceptions
-----------------------------------------------------------
Key: JBSEAM-3883
URL: https://jira.jboss.org/jira/browse/JBSEAM-3883
Project: Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.1.1.GA
Reporter: Stephen Friedrich
When a configured exception handler redirects to a view-id, then the URL for that view-id is not processed by Seam's URL rewriting filter.
As a result you cannot re-write the URL for your login page if you want to redirect to the login page when a ViewExpiredSException occurs.
The problem is that the RewriteFilter is deeper in the filter chain than the ExceptionFilter, so at the time when the exception filter is handling an exception no RewritingResponse is on the chain of wrapped responses.
Norman RIchards suggested to split incoming and outgoing rewriting and place it at opposite ends of the filter chain.
--
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, 3 months