September 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBDEPLOY-264) Allow for explicit attachment key definition on parse deployer's output

by Ales Justin (JIRA)

Allow for explicit attachment key definition on parse deployer's output ----------------------------------------------------------------------- Key: JBDEPLOY-264 URL: https://jira.jboss.org/browse/JBDEPLOY-264 Project: JBoss Deployers Issue Type: Task Components: attachments, deployer Reporter: Ales Justin Assignee: Ales Justin Fix For: JBDEPLOY-2.2.0.Beta1 Allow for explicit attachment key definition on parse deployer's output -- @AttachmentKey(FooBar.class.getName()). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCL-170) Cache resolved requirement dependency items

by Ales Justin (JIRA)

Cache resolved requirement dependency items ------------------------------------------- Key: JBCL-170 URL: https://jira.jboss.org/browse/JBCL-170 Project: JBoss ClassLoader Issue Type: Task Components: Modules Reporter: Ales Justin Assignee: Ales Justin Fix For: JBossCL.2.2.0.Beta1 Cache resolved requirement dependency items in Module. Since item resolution can also come from resolving ClassLoadingSpace. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCL-171) Remove loaded class's cache item from vfsCache in VFSClassLoaderPolicy

by Ales Justin (JIRA)

Remove loaded class's cache item from vfsCache in VFSClassLoaderPolicy ---------------------------------------------------------------------- Key: JBCL-171 URL: https://jira.jboss.org/browse/JBCL-171 Project: JBoss ClassLoader Issue Type: Task Components: ClassLoaderPolicy Reporter: Ales Justin Assignee: Ales Justin Fix For: JBossCL.2.2.0.Beta1 Remove loaded class's cache item from vfsCache in VFSClassLoaderPolicy, as the class is already cached in ClassLoader, hence no need for resource lookup. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCL-173) Allow for wildcard root in <classloader>

by Ales Justin (JIRA)

Allow for wildcard root in <classloader> ---------------------------------------- Key: JBCL-173 URL: https://jira.jboss.org/browse/JBCL-173 Project: JBoss ClassLoader Issue Type: Feature Request Components: ClassLoader, MetaData, VFS Reporter: Ales Justin Assignee: Ales Justin Fix For: JBossCL.2.2.0.Beta1 We should be able to support wildcards in <classloader>'s root element. e.g. <classloader xmlns="urn:jboss:classloader:1.0" name="wc"> <root>${test.dir}/*.jar</root> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBCL-172) Check for null result before sending class found event

by Ales Justin (JIRA)

Check for null result before sending class found event ------------------------------------------------------ Key: JBCL-172 URL: https://jira.jboss.org/browse/JBCL-172 Project: JBoss ClassLoader Issue Type: Bug Components: ClassLoader, ClassLoaderPolicy Reporter: Ales Justin Assignee: Ales Justin Fix For: JBossCL.2.2.0.Beta1 There is a potential NPE if the loadClassLocally has no matching input stream. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBCL-174) Optimize explicit imports cache

by Ales Justin (JIRA)

Optimize explicit imports cache ------------------------------- Key: JBCL-174 URL: https://jira.jboss.org/browse/JBCL-174 Project: JBoss ClassLoader Issue Type: Task Components: ClassLoader Reporter: Ales Justin Assignee: Ales Justin Fix For: JBossCL.2.2.0.Beta1 Currently explicit imports don't use any cache, which makes it slower to use wrt Import.ALL. We should try adding some cache to ClassLoadingSpace, which properly delegate shared packages, hence can share common cache. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCL-160) Split imports into before and after local lookup

by Ales Justin (JIRA)

Split imports into before and after local lookup ------------------------------------------------ Key: JBCL-160 URL: https://jira.jboss.org/jira/browse/JBCL-160 Project: JBoss ClassLoader Issue Type: Feature Request Components: ClassLoader Reporter: Ales Justin Assignee: Ales Justin In OSGi dynamic imports come after local lookup. We currently check all imports before local lookup, this should be split into before and after; to still maintain back compatibility, while also properly handling OSGi behavior (which would define imports as after). -- 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

13 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2125) Non public timeouts method invocations fail for EJB3 beans

by jaikiran pai (JIRA)

Non public timeouts method invocations fail for EJB3 beans ---------------------------------------------------------- Key: EJBTHREE-2125 URL: https://jira.jboss.org/browse/EJBTHREE-2125 Project: EJB 3.0 Issue Type: Bug Components: core Affects Versions: EJB3_1 1.0.7 Reporter: jaikiran pai Assignee: jaikiran pai Fix For: EJB3_1 1.0.8 As mentioned in EJBTHREE-1733: <quote> Another bug - private timeout methods on the bean aren't invoked by the timerservice impl. The spec allows for such invocations: EJB3.1 Spec, 18.2.5.3: A timeout callback method can have public, private, protected, or package level access. A timeout callback method must not be declared as final or static. </quote> Creating this new JIRA for tracking this specific issue separately. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2143) EjbResolver must support no-interface view lookup

by Marius Bogoevici (JIRA)

EjbResolver must support no-interface view lookup ------------------------------------------------- Key: EJBTHREE-2143 URL: https://jira.jboss.org/browse/EJBTHREE-2143 Project: EJB 3.0 Issue Type: Bug Components: nointerface Reporter: Marius Bogoevici It currently works only if the bean has an interface. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2138) TimeoutMethodCallbackRequirements doesn't take into account the timeout method parameters

by jaikiran pai (JIRA)

TimeoutMethodCallbackRequirements doesn't take into account the timeout method parameters ----------------------------------------------------------------------------------------- Key: EJBTHREE-2138 URL: https://jira.jboss.org/browse/EJBTHREE-2138 Project: EJB 3.0 Issue Type: Bug Components: timeout Affects Versions: bom-eap5-0.1.2, EJB3_1 1.0.7 Reporter: jaikiran pai Assignee: jaikiran pai Consider the following base class: public class Base { protected void onTimeout() { ... } } and a EJB impl class which extends it: @Stateless public class Bean extends Base { protected void onTimeout(Timer timer) { // This one should *not* be picked up, based on the ejb-jar.xml } } and the corresponding ejb-jar.xml which marks the onTimeout() method (the one in Base class without any params) as the timeout callback method: <timeout> <method-name>onTimeout</method-name> <method-params> </method-params> </timeout> Based on this configuration and code, the Base.onTimeout() method must be chosen as the timeout callback method, but because of the lack of information of method param types, the TimeoutMethodCallbackRequirements, incorrectly, ends up picking the Bean.onTimeout(Timer timer) method as the timeout callback method. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2010