November 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4961) Default for JBossCacheManager useJK is whether jvmRoute is set

by Brian Stansberry (JIRA)

Default for JBossCacheManager useJK is whether jvmRoute is set -------------------------------------------------------------- Key: JBAS-4961 URL: http://jira.jboss.com/jira/browse/JBAS-4961 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: JBossAS-5.0.0.Beta3 Having to configure "useJK" for the JBossWeb service is redundant, since Engine.jvmRoute is null by default. Treat having Engine.jvmRoute set as meaning JBossCacheManager should add the JvmRouteValve. Allow override via JBossWebMetaData (jboss-web.xml). -- 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

17 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4993) org.jboss.tm.test.

by Shelly McGowan (JIRA)

org.jboss.tm.test. ------------------ Key: JBAS-4993 URL: http://jira.jboss.com/jira/browse/JBAS-4993 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Shelly McGowan -- 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

17 years, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1779) SynchronizingLoginModule prevents access to Dashboard

by Guy M. Spillman, Jr. (JIRA)

SynchronizingLoginModule prevents access to Dashboard ----------------------------------------------------- Key: JBPORTAL-1779 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1779 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Security Affects Versions: 2.6.2 Final Environment: Pentium 3 - 2GB memroy - 20 GB of Free Space Windows XP Professional Service Pack 2 JBoss Portal 2.6.2 + JBoss AS 4.2.1 Bundle Reporter: Guy M. Spillman, Jr. Assigned To: Julien Viet Users who athenticate using an additional login module after the IdentityLoginModule get the following HTTP error when clicking on their Dashboard link: HTTP Status 403 - -------------------------------------------------------------------------------- type Status report message description Access to the specified resource () has been forbidden. -------------------------------------------------------------------------------- JBossWeb/2.0.0.GA Users who login with the IdentityLoginModule (such as the default user & admin usernames) will see their Dashboard content without problems. Problem was discovered using JaasLounge(http://jaaslounge.sourceforge.net/ ) NTLMLoginModule, but can be duplicated using JBoss' UsersRolesLoginModule. This problem was originally discussed in the following thread, but seams to be a different problem since it can be duplicated using JBoss code only. http://www.jboss.com/index.html?module=bb&op=viewtopic&t=119733 Configuration: ${jboss.server.home.dir}\deploy\jboss-portal.sar\conf\login-config.xml: Code: <login-module code="org.jboss.portal.identity.auth.IdentityLoginModule" flag="sufficient"> <module-option name="unauthenticatedIdentity">guest</module-option> <module-option name="userModuleJNDIName">java:/portal/UserModule</module-option> <module-option name="roleModuleJNDIName">java:/portal/RoleModule</module-option> <module-option name="userProfileModuleJNDIName">java:/portal/UserProfileModule</module-option> <module-option name="membershipModuleJNDIName">java:/portal/MembershipModule</module-option> <module-option name="additionalRole">Authenticated</module-option> <module-option name="password-stacking">useFirstPass</module-option> </login-module> <login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule" flag="required" /> <login-module code="org.jboss.portal.identity.auth.SynchronizingLoginModule" flag="optional"> <module-option name="synchronizeIdentity">true</module-option> <module-option name="synchronizeRoles">false</module-option> <module-option name="additionalRole">Authenticated</module-option> <module-option name="defaultAssignedRole">User</module-option> <module-option name="userModuleJNDIName">java:/portal/UserModule</module-option> <module-option name="roleModuleJNDIName">java:/portal/RoleModule</module-option> <module-option name="membershipModuleJNDIName">java:/portal/MembershipModule</module-option> <module-option name="userProfileModuleJNDIName">java:/portal/UserProfileModule</module-option> </login-module> ${jboss.server.home.dir}\conf\defaultRoles.properties: Code: testuser=test testuser2=test2 ${jboss.server.home.dir}\conf\defaultUsers.properties: Code: testuser=testrole1,testrole2 testuser2=testrole3,testrole4 Procedure: 1. Login a testuser/test. 2. Click Dashboard link. The HTTP Status 403 error described above will be displayed. -- 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

17 years, 1 month

3
5
0 / 0

[JBoss JIRA] Created: (JBRULES-1350) Support for decision tables in ant-drools

by Matija Kejzar (JIRA)

Support for decision tables in ant-drools ----------------------------------------- Key: JBRULES-1350 URL: http://jira.jboss.com/jira/browse/JBRULES-1350 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Decision tables Affects Versions: 4.0.3 Reporter: Matija Kejzar Request for enhancement: The drools-ant ant extension currently doesn't support decision tables (either .xls or .csv) compilation and serialization. It would be nice to have that in order to fully leverage non-source rule deployment capabilities of Drools. -- 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

17 years, 1 month

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-3818) Application Client Container capabilities may be useful

by Mike Khlu (JIRA)

Application Client Container capabilities may be useful ------------------------------------------------------- Key: JBAS-3818 URL: http://jira.jboss.com/jira/browse/JBAS-3818 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: EJB3, Other Reporter: Mike Khlu Assigned To: Bill Burke Now we have pretty nice @EJB annotation within there no the ugly JNDI-client code required. please look at http://java.sun.com/j2ee/1.4/docs/relnotes/cliref/hman1m/appclient.1m.html and "Creating a Reference to an Enterprise Bean Instance" chapter on J2ee 5 Sun's tutorial. I think that would be great to have application client container's possibilities in the best app server (aka JBoss)!!! sorry, my english isn't glance -- 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

17 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4707) Convert ClientDeployer to a AbstractVFSParsingDeployer subclass

by Scott M Stark (JIRA)

Convert ClientDeployer to a AbstractVFSParsingDeployer subclass --------------------------------------------------------------- Key: JBAS-4707 URL: http://jira.jboss.com/jira/browse/JBAS-4707 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Deployment services Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossAS-5.0.0.Beta3 The org.jboss.deployment.ClientDeployer needs to be a AbstractVFSParsingDeployer that outputs ClientMetaData -- 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

17 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1030) Implement EE 8.2.1 section 2 functionality

by Carlo de Wolf (JIRA)

Implement EE 8.2.1 section 2 functionality ------------------------------------------ Key: EJBTHREE-1030 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1030 Project: EJB 3.0 Issue Type: Sub-task Reporter: Carlo de Wolf Fix For: EJB 3.0 RC11 - FD -- 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

17 years, 1 month

1
4
0 / 0

[JBoss JIRA] Created: (JBAS-4424) WebAuthentication:Generate a SSOID

by Anil Saldhana (JIRA)

WebAuthentication:Generate a SSOID ---------------------------------- Key: JBAS-4424 URL: http://jira.jboss.com/jira/browse/JBAS-4424 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Security, Web (Tomcat) service Affects Versions: JBossAS-4.2.0.GA Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: JBossAS-4.2.1.CR1 http://wiki.jboss.org/wiki/Wiki.jsp?page=WebAuthentication The feature needs to implement the sso stuff if it is desired by the user. At the least, ssoid needs to be generated and set on the session. The ssoid generation logic exists in AuthenticatorBase. -- 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

17 years, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBCACHE-1224) Wrong Connection in JDBCCacheLoader

by Carsten Mjartan (JIRA)

Wrong Connection in JDBCCacheLoader ----------------------------------- Key: JBCACHE-1224 URL: http://jira.jboss.com/jira/browse/JBCACHE-1224 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Cache loaders Affects Versions: 1.4.1.SP6, 1.4.1.SP5 Environment: 2 TreeCaches, each having 1 JDBCCacheLoader (passivation) using a different database Reporter: Carsten Mjartan Assigned To: Manik Surtani I configured 2 JBossCaches as stated above. Both use CacheLoaders which use different Database Backends (using hsqldb) and with table creation turned on. After Startup both tables are created using the cached connection of the first cacheloader, so the second cacheloader goes mad. I solved this for me by copying JDBCCacheLoader and replacing the ThreadLocal "connection" with a ThreadLocal Connection-Map using the url as the key, but I don't know if this may cause other problems (open connections?). -- 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

17 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-1223) JDBCExtendedCacheLoader does not fully support RegionBasedMarshalling

by Carsten Mjartan (JIRA)

JDBCExtendedCacheLoader does not fully support RegionBasedMarshalling --------------------------------------------------------------------- Key: JBCACHE-1223 URL: http://jira.jboss.com/jira/browse/JBCACHE-1223 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Cache loaders Affects Versions: 1.4.1.SP5 Environment: JBoss 4.2.2 with JBossCache 1.4.1SP5, own EvictionPolicy, RegionBasedMarshalling and ClassLoaders used, JDBCExtendedCacheLoader with cache passivation configured Reporter: Carsten Mjartan Assigned To: Manik Surtani JDBCExtendedCacheLoader does not override the loadNode() method to replace the thread's context classloader based on the region. So I',m getting classloading exceptions during cache eviction. loadNode() should change to protected for this to work. -- 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

17 years, 1 month

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2007