November 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3577) Security SPI

by Anil Saldhana (JIRA)

Security SPI ------------- Key: JBAS-3577 URL: http://jira.jboss.com/jira/browse/JBAS-3577 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Anil Saldhana Assigned To: Anil Saldhana We have to define a JBoss Security SPI that can be utilized by service providers. The SPI should take into consideration: a) Role Mapping. b) Auditing Functionaility. c) Identity Mapping Functionality. (Security Token which can be binary to a Principal) d) Principal Mapping Functionality. e) Certificate Mapping. (X509 cert to a Principal). others.... -- 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, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBCACHE-860) Clustered Cache Loaders too "noisy" with error level logging when alone in the cluster

by Manik Surtani (JIRA)

Clustered Cache Loaders too "noisy" with error level logging when alone in the cluster -------------------------------------------------------------------------------------- Key: JBCACHE-860 URL: http://jira.jboss.com/jira/browse/JBCACHE-860 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Cache loaders Affects Versions: 1.4.0.SP1 Reporter: Manik Surtani Assigned To: Manik Surtani Priority: Minor Fix For: 1.4.1.GA, 2.0.0.GA -- 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, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPM-752) hibernate warnings in update HQL statements

by Alex Burgel (JIRA)

hibernate warnings in update HQL statements ------------------------------------------- Key: JBPM-752 URL: http://jira.jboss.com/jira/browse/JBPM-752 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM 3.1.2 Reporter: Alex Burgel Assigned To: Tom Baeyens Priority: Trivial i'm seeing a bunch of hibernate warnings in jbpm 3.1.2, with hibernate 3.1.3: FromElementType - Using non-qualified column reference [id -> ([ID_])] FromElementType - Using non-qualified column reference [isSuspended -> ([ISSUSPENDED_])] FromElementType - Using non-qualified column reference [token -> ([TOKEN_])] FromElementType - Using non-qualified column reference [isSuspended -> ([ISSUSPENDED_])] FromElementType - Using non-qualified column reference [token -> ([TOKEN_])] FromElementType - Using non-qualified column reference [isSuspended -> ([ISSUSPENDED_])] FromElementType - Using non-qualified column reference [token -> ([TOKEN_])] FromElementType - Using non-qualified column reference [isSuspended -> ([ISSUSPENDED_])] FromElementType - Using non-qualified column reference [token -> ([TOKEN_])] FromElementType - Using non-qualified column reference [processInstance -> ([PROCESSINSTANCE_])] they are caused by update HQL statements in org.jbpm.db.hibernate.queries.hbm.xml. i think for update statements you have to be explicit about column references. you have to specify the table name or alias for each column, otherwise you'll get these warnings. -- 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, 8 months

1
1
0 / 0

[JBoss JIRA] Commented: (JBPM-682) task forms are not reloaded when a process is reloaded

by David Lloyd (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-682?page=comments#action_12347336 ] David Lloyd commented on JBPM-682: ---------------------------------- Tom fixed it. The URL was basically the name of the file within the process archive, but since facelets caches by URL, once the process form was displayed it would be cached even though the URL provider changed. Tom added the process ID in to the URL, and that fixed the problem. > task forms are not reloaded when a process is reloaded > ------------------------------------------------------ > > Key: JBPM-682 > URL: http://jira.jboss.com/jira/browse/JBPM-682 > Project: JBoss jBPM > Issue Type: Bug > Components: Web Interface > Affects Versions: jBPM 3.2 alpha 1 > Environment: JBoss 4.03, jBPM 3.2 cvshead, jdk 1.5 > Reporter: Ronald van Kuijk > Assigned To: David Lloyd > Priority: Blocker > Fix For: jBPM 3.2 alpha 2 > > > tom: this has to do with the caching of the task forms. > kukeltje: At first the forms seem to be 'versionable' like the process archive. When trying to use this, it does not work. > If I have an error in a form, correct it and deploy a new process, the new form is stored in the DB. If I start a new pi for the latest pd, the previous version of the form seems to be cached by something however and used for the new process (form name stays the same). If I stop the server and start it again, start a new instance of the latest process (or load one for which I'm sure a correct form is present, the correct form is used. The tasks in older instances which should use the old forms can now be executed as well (meaning they use the new form). -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-3321) Support for "method-attributes" including "transaction-timeout" for MDBs

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3321?page=comments#action_12347328 ] Adrian Brock commented on JBAS-3321: ------------------------------------ "Can't you change the TX timeout within the transaction?" No. > Support for "method-attributes" including "transaction-timeout" for MDBs > ------------------------------------------------------------------------ > > Key: JBAS-3321 > URL: http://jira.jboss.com/jira/browse/JBAS-3321 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: EJB2 > Affects Versions: JBossAS-4.0.4.GA > Reporter: Galder Zamarreno > Assigned To: Scott M Stark > > Looking at jboss_4_0.dtd it seems that MDBs in JBoss do not support the use of "method-attributes", > particularly "transaction-timeout", why is this? > I have looked in to this a little and it doesn't seem to be prohibited by the J2EE specs, in fact > Weblogic seems to support the setting of transaction timeouts on MDBs, so why not JBoss? > I guess it is either an error or a deliberate design decision not to support it, if it's the latter I > would be interested to hear what the rational is? > Adrian Brock wrote: > Because the MDB transaction is not started by the EJB container > like the other EJB types. > Raise a feature request. There is no reason why the ServerSessionPool > cannot ask the EJB container for this information. > _________________ > Adrian Brock > Chief Scientist > JBoss, Inc. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-682) task forms are not reloaded when a process is reloaded

by David Lloyd (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-682?page=comments#action_12347327 ] David Lloyd commented on JBPM-682: ---------------------------------- I think that any process definition metadata should be keyed off of nothing but the process definition ID (since a new ID is assigned for every version of a process definition). This is what i currently do internally on the web console... now the question is, why is that not working. One other clue is that "view task form source" seems to find the updated task form. Hmmm. > task forms are not reloaded when a process is reloaded > ------------------------------------------------------ > > Key: JBPM-682 > URL: http://jira.jboss.com/jira/browse/JBPM-682 > Project: JBoss jBPM > Issue Type: Bug > Components: Web Interface > Affects Versions: jBPM 3.2 alpha 1 > Environment: JBoss 4.03, jBPM 3.2 cvshead, jdk 1.5 > Reporter: Ronald van Kuijk > Assigned To: David Lloyd > Priority: Blocker > Fix For: jBPM 3.2 alpha 2 > > > tom: this has to do with the caching of the task forms. > kukeltje: At first the forms seem to be 'versionable' like the process archive. When trying to use this, it does not work. > If I have an error in a form, correct it and deploy a new process, the new form is stored in the DB. If I start a new pi for the latest pd, the previous version of the form seems to be cached by something however and used for the new process (form name stays the same). If I stop the server and start it again, start a new instance of the latest process (or load one for which I'm sure a correct form is present, the correct form is used. The tasks in older instances which should use the old forms can now be executed as well (meaning they use the new form). -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-3321) Support for "method-attributes" including "transaction-timeout" for MDBs

by Bill Burke (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3321?page=comments#action_12347322 ] Bill Burke commented on JBAS-3321: ---------------------------------- We support this in EJB 3.0 already: @org.jboss.annotation.ejb.TransactionTimeout or the old way in jboss.xml <method-attributes> <method> <method-name>testTransactionTimeout</method-name> <transaction-timeout>1</transaction-timeout> </method> </method-attributes> BTW, why does this adapter need to handle this? Can't you change the TX timeout within the transaction? > Support for "method-attributes" including "transaction-timeout" for MDBs > ------------------------------------------------------------------------ > > Key: JBAS-3321 > URL: http://jira.jboss.com/jira/browse/JBAS-3321 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: EJB2 > Affects Versions: JBossAS-4.0.4.GA > Reporter: Galder Zamarreno > Assigned To: Scott M Stark > > Looking at jboss_4_0.dtd it seems that MDBs in JBoss do not support the use of "method-attributes", > particularly "transaction-timeout", why is this? > I have looked in to this a little and it doesn't seem to be prohibited by the J2EE specs, in fact > Weblogic seems to support the setting of transaction timeouts on MDBs, so why not JBoss? > I guess it is either an error or a deliberate design decision not to support it, if it's the latter I > would be interested to hear what the rational is? > Adrian Brock wrote: > Because the MDB transaction is not started by the EJB container > like the other EJB types. > Raise a feature request. There is no reason why the ServerSessionPool > cannot ask the EJB container for this information. > _________________ > Adrian Brock > Chief Scientist > JBoss, Inc. -- 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, 8 months

1
0
0 / 0

[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.alpha3 (was: 2.0.0.alpha2) > ${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.alpha3 > > 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, 8 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBAOP-109) AOP/MC integration tests

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-109?page=all ] Kabir Khan closed JBAOP-109. ---------------------------- Resolution: Done Assignee: Kabir Khan > AOP/MC integration tests > ------------------------ > > Key: JBAOP-109 > URL: http://jira.jboss.com/jira/browse/JBAOP-109 > Project: JBoss AOP > Issue Type: Task > Components: Aspect Library > Reporter: Adrian Brock > Assigned To: Kabir Khan > Fix For: 2.0.0.alpha2 > > > Write some simple testcases that show the basic use cases > that require MC/AOP integration vs just using AOP in its current format. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAOP-308) Default values for mc annotations not picked up when running in jboss

by Kabir Khan (JIRA)

Default values for mc annotations not picked up when running in jboss --------------------------------------------------------------------- Key: JBAOP-308 URL: http://jira.jboss.com/jira/browse/JBAOP-308 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.0.0.alpha2 This is because the AnnotationValidator used is the non-javassist one since javassist is not part of the boot jars. -- 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, 8 months

1
3
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 November 2006