seam-issues March 2009

seam-issues@lists.jboss.org

1 participants
574 discussions

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3985) NullPointerException on ClassIdentifierStrategy

by douglas carvalho (JIRA)

NullPointerException on ClassIdentifierStrategy ----------------------------------------------- Key: JBSEAM-3985 URL: https://jira.jboss.org/jira/browse/JBSEAM-3985 Project: Seam Issue Type: Bug Affects Versions: 2.1.1.GA Reporter: douglas carvalho Class: ClassIdentifierStrategy in seam security The code does "equals(name.trim()))", but sinse name is null, as done in the begin of the code block, it throws a nullPointerException. private String getIdentifierName(Class cls) { if (!identifierNames.containsKey(cls)) { String name = null; if (cls.isAnnotationPresent(Identifier.class)) { Identifier identifier = (Identifier) cls.getAnnotation(Identifier.class); if (identifier.name() != null && !"".equals(name.trim())) { name = identifier.name(); } } ... -- 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, 3 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1918) Asyncronous methods called from an asyncronously executing methoed will not be invoke asyncronously

by Chris Rudd (JIRA)

Asyncronous methods called from an asyncronously executing methoed will not be invoke asyncronously --------------------------------------------------------------------------------------------------- Key: JBSEAM-1918 URL: http://jira.jboss.com/jira/browse/JBSEAM-1918 Project: JBoss Seam Issue Type: Bug Components: Async Affects Versions: 2.0.0.BETA1 Reporter: Chris Rudd Currently the AsyncronousInterceptor triggers off of Contexts.getEventContext().isSet(AbstractDispatcher.EXECUTING_ASYNCHRONOUS_CALL) to determine if this invocation was from the asyncronous dispatcher. This works fine, except under the conditions where the asyncronously executed method calls another @asyncronous methd. In that case the Event context alreadt contains the AbstractDispatcher.EXECUTING_ASYNCHRONOUS_CALL marked and the execution is done immedialty instead of being scheduled. I belive a simple resolution would be to have the AsyncronousInterceptor clear the AbstractDispatcher.EXECUTING_ASYNCHRONOUS_CALL before proceeding with the exection, but should only be done if the method in question is an @Asycnronous method. This would be to elimiate possible removal from other components that are called during the process of invoking the asyncronous method (ie injection, security, etc). Here is me proposed change : AsyncronousInterceptor.java line 24 @AroundInvoke public Object aroundInvoke(InvocationContext invocation) throws Exception { boolean scheduleAsync = invocation.getMethod().isAnnotationPresent(Asynchronous.class) && !Contexts.getEventContext().isSet(AbstractDispatcher.EXECUTING_ASYNCHRONOUS_CALL); if (scheduleAsync) { Dispatcher dispatcher = AbstractDispatcher.instance(); if (dispatcher==null) { throw new IllegalStateException("org.jboss.seam.async.dispatcher is not installed in components.xml"); } Object timer = dispatcher.scheduleInvocation( invocation, getComponent() ); //if the method returns a Timer, return it to the client return timer!=null && invocation.getMethod().getReturnType().isAssignableFrom( timer.getClass() ) ? timer : null; } + else if( invocation.getMethod().isAnnotationPresent(Asynchronous.class) ) + { + // Clear the async flag so that any async methods called by this invocation will execute asyncronously + Contexts.getEventContext().remove( AbstractDispatcher.EXECUTING_ASYNCHRONOUS_CALL ); + return invocation.proceed(); + } else { return invocation.proceed(); } } -- 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

15 years, 3 months

4
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3969) Document web vulnerabilities

by Christian Bauer (JIRA)

Document web vulnerabilities ---------------------------- Key: JBSEAM-3969 URL: https://jira.jboss.org/jira/browse/JBSEAM-3969 Project: Seam Issue Type: Task Components: Documentation Issues Reporter: Christian Bauer Assignee: Christian Bauer Marc Schoenefeld has written a "Web Vulnerabilities, 101" document. Further steps: - Create individual wiki pages for each vulnerability category - Proofread and transform the content from the paper - Add additional sections to each page how each vulnerability might affect Seam users and what they can do about it -- 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, 3 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3982) asynchronous interceptor reentrant flag not reset correctly

by Norman Richards (JIRA)

asynchronous interceptor reentrant flag not reset correctly ----------------------------------------------------------- Key: JBSEAM-3982 URL: https://jira.jboss.org/jira/browse/JBSEAM-3982 Project: Seam Issue Type: Bug Reporter: Norman Richards Assignee: Norman Richards Priority: Minor Fix For: 2.1.2.CR1 See comments at JBSEAM-1918 -- 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, 3 months

1
1
0 / 0

← Newer
1
...
55
56
57
58
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues March 2009