June 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBAOP-243) ${instanceof} disregards method call target

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-243?page=all ] Kabir Khan updated JBAOP-243: ----------------------------- Fix Version/s: 2.0.0.alpha6 (was: 2.0.0.alpha5) > ${instanceof} disregards method call target > ------------------------------------------- > > Key: JBAOP-243 > URL: http://jira.jboss.com/jira/browse/JBAOP-243 > Project: JBoss AOP > Issue Type: Bug > Affects Versions: 1.3.5 > Reporter: Konstantin Sobolev > Assigned To: Kabir Khan > Fix For: 2.0.0.alpha6 > > Attachments: jbaop-243.tar.gz > > > instanceof{$I}->method() checks a class declaring method() instead of the class on which this method is actually called. > Example: > interface I1 {void foo();} > interface I2 {void bar();} > class I1Impl implements I1 {void foo(){};} > class Target extends I1Impl implements I2 {void bar();} > now $instanceof{I1}->foo() will intercept new Target.foo(), while > ${instanceof{I1}->bar() won't intercept new Target.bar(). > Testcase implementing this example is attached. > Please see forum thread for a real life example. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBAOP-107) The different types of classloader integration for AOP belong in the related release not jboss-head

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-107?page=all ] Kabir Khan updated JBAOP-107: ----------------------------- Fix Version/s: 2.0.0.alpha6 (was: 2.0.0.alpha5) > The different types of classloader integration for AOP belong in the related release not jboss-head > --------------------------------------------------------------------------------------------------- > > Key: JBAOP-107 > URL: http://jira.jboss.com/jira/browse/JBAOP-107 > Project: JBoss AOP > Issue Type: Task > Affects Versions: 2.0.0.alpha4 > Reporter: Adrian Brock > Assigned To: Kabir Khan > Priority: Minor > Fix For: 2.0.0.alpha6 > > > The JBoss classloading integration with JBossAOP should be managed by JBoss release, > not by the aop/aspects modules in jboss-head. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBAOP-385) Uniformize Advice Exception Treatment

by Flavia Rainone (JIRA)

Uniformize Advice Exception Treatment ------------------------------------- Key: JBAOP-385 URL: http://jira.jboss.com/jira/browse/JBAOP-385 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Flavia Rainone Assigned To: Flavia Rainone Priority: Minor Fix For: 2.0.0.alpha5 The treatment of exceptions in PerVMAdvice is different from the one in JoinPointGenerator. We need to pick one of them and use the same approach on both cases. -- 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, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (JGRP-531) Resource loading issue

by Bela Ban (JIRA)

Resource loading issue ---------------------- Key: JGRP-531 URL: http://jira.jboss.com/jira/browse/JGRP-531 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assigned To: Bela Ban Priority: Minor Fix For: 2.5 Recently I encountered a resource loading problem from within a tomcat webapp when trying to construct a JChannel when so triggered from a JMX MBean via the jconsole: channel = new JChannel("tcp.xml"); Basically if the JChannel is constructed from a webapp, it can locate the "tcp.xml" from the classpath as a resource and works just fine. However if the JChannel is constructed from an MBean call stack via the jconsole, it failed to locate the resource due to the fact that the context classloading of the executing thread is different. So I hacked Util.java and it now worked in both cases. See below for details. My question is should the hack I made be incorporated into the official version ? (I hacked this on jgroups 2.2.9.4 , but I tried the latest 2.5.0CR1 which also seems to exhibit the same problem/behavior.) Hanson Char org.jgroups.util.Util.java ================= public static InputStream getResourceAsStream(String name, Class clazz) { ClassLoader loader; try { loader=Thread.currentThread().getContextClassLoader(); if(loader != null) { // hanson: returns only if resource is found // return loader.getResourceAsStream(name); InputStream is = loader.getResourceAsStream(name); if (is != null) return is; } } catch(Throwable t) { } if(clazz != null) { try { loader=clazz.getClassLoader(); if(loader != null) { // hanson: returns only if resource is found // return loader.getResourceAsStream(name); InputStream is = loader.getResourceAsStream(name); if (is != null) return is; } } catch(Throwable t) { } } try { loader= ClassLoader.getSystemClassLoader(); if(loader != null) { return loader.getResourceAsStream(name); } } catch(Throwable t) { } return null; } -- 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, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (SECURITY-63) JACC: Security Constraint missing an auth-constraint needs an unchecked permission

by Anil Saldhana (JIRA)

JACC: Security Constraint missing an auth-constraint needs an unchecked permission ---------------------------------------------------------------------------------- Key: SECURITY-63 URL: http://jira.jboss.com/jira/browse/SECURITY-63 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: AS-Integration Affects Versions: 2.0.GA Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.1.BETA Given a snippet <security-constraint> <web-resource-collection> <web-resource-name>MyBit4</web-resource-name> <url-pattern>/unchecked.jsp</url-pattern> <http-method>POST</http-method> <http-method>GET</http-method> </web-resource-collection> <user-data-constraint> <transport-guarantee>NONE</transport-guarantee> </user-data-constraint> </security-constraint> This requires an unchecked permission added to the policy as follows: WebResourcePermission("/unchecked.jsp", (String) null)) -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-62) Distinguish between incoming and outgoing RunAs into a security context

by Anil Saldhana (JIRA)

Distinguish between incoming and outgoing RunAs into a security context ----------------------------------------------------------------------- Key: SECURITY-62 URL: http://jira.jboss.com/jira/browse/SECURITY-62 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Security SPI Affects Versions: 2.0.GA Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.1.BETA RunAs can propagate into a security context from an external context. And also a particular RunAs may be configured to be propagated out of the security context in question. -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1397) WSRP Consumer configuration GUI improvements

by Chris Laprun (JIRA)

WSRP Consumer configuration GUI improvements -------------------------------------------- Key: JBPORTAL-1397 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1397 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.CR2 Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.6 Final Chris DeLashmutt says: In the WSRP page, the pages portlet should be removed as it duplicates the same information as is in the Navigation tabs. Configured WSRP Consumers View Need more horizontal spacing between the "Create a consumer named:" label and the text box it is a label for. Need more vertical spacing between the consumer creation UI elements, and then defined consumer list. The Legend for the consumer list should not be (or appear to be) a row within the consumer list. This element should be below or above the consumer list. Linking the consumer name and providing an Action called "Configure" that both go to the same function is redundant. Either remove the Configure action or un-link the consumer name. The actions for the consumer should not be styled the same as the consumer name. I could cause confusion as users may percieve the actions are "active", "inactive", or "need refresh". There should be a space after the "pipe" separator in the WSRP consumer list to be consistent with the other action lists in the administrative portal. Consider using icon images (with alt attributes set to the name of the function) for actions in the list. Configuration View The form labels in this view are inconsistent with all the other field labels in the portlets in the administrative portal. I'm not saying they are bad (in fact, I personally prefer the style of these labels over the others), but they need to be made consistent with the rest of the admin portal labels, or the rest of the admin portal labels should be made to look like these labels. The vertical bars in front of the fields in this view are inconsistent with all of the other fields in the admin portal. The bars need to be removed. The buttons "Refresh", "Activate" and "Destroy" shouldn't be in the view that deals with changing the configuration of a WSRP consumer. These buttons should be removed. The "Save" and "Return to list" buttons should be on the left-bottom side of the portlet, and they should be sized, aligned, and padded consistently. The "Return to list" button label should be changed to "Cancel". -- 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, 1 month

1
3
0 / 0

[JBoss JIRA] Updated: (JBPM-158) Add <description> back into jPDL

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-158?page=all ] Ronald van Kuijk updated JBPM-158: ---------------------------------- Fix Version/s: jBPM 3.3 > Add <description> back into jPDL > -------------------------------- > > Key: JBPM-158 > URL: http://jira.jboss.com/jira/browse/JBPM-158 > Project: JBoss jBPM > Issue Type: Task > Components: Core Engine > Affects Versions: jBPM 3.0 > Environment: All > Reporter: Jim Rigsbee > Assigned To: Tom Baeyens > Priority: Minor > Fix For: jBPM 3.3 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > A description element was supported in 2.0. This does not exist in 3.0 so far. > We need to decide whether it should go in and to what extent. In 2.0 it was available on every major element. I would like to suggest that we support it only on the process-definition itself, as people can use <! xxx ---> style comments anywhere they choose. > Perhaps this needs to be coordinated with tasks surrounding features for versioning, etc. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-1101) PessimisticLocakInterceptor nukes the transaction entry before NotificationInterceptor delivers

by Jason T. Greene (JIRA)

PessimisticLocakInterceptor nukes the transaction entry before NotificationInterceptor delivers ----------------------------------------------------------------------------------------------- Key: JBCACHE-1101 URL: http://jira.jboss.com/jira/browse/JBCACHE-1101 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Jason T. Greene Assigned To: Manik Surtani Fix For: 2.0.0.CR3, 2.0.0.GA Whenever a transaction is committed, PessimisticLockInterceptor calls cleanup on line 221, which purges the TX entry. Since NotificaitonInterceptor operates on return, delivery happens after the cleanup call, resulting in no notifications being sent. While the lock interceptor should release all locks, the tx entry should perhaps be removed by the TxInterceptor instead. -- 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, 1 month

2
2
0 / 0

[JBoss JIRA] Updated: (JBAOP-253) Before release, submit the jar to the Messaging team for testing

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-253?page=all ] Kabir Khan updated JBAOP-253: ----------------------------- Fix Version/s: 2.0.0.alpha6 (was: 2.0.0.alpha5) > Before release, submit the jar to the Messaging team for testing > ---------------------------------------------------------------- > > Key: JBAOP-253 > URL: http://jira.jboss.com/jira/browse/JBAOP-253 > Project: JBoss AOP > Issue Type: Task > Reporter: Ovidiu Feodorov > Assigned To: Kabir Khan > Fix For: 2.0.0.alpha6 > > -- 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, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2007