April 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Assigned: (JBAS-2315) Create an automated test for JBAS-2314

by Hany Mesha (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2315?page=all ] Hany Mesha reassigned JBAS-2315: -------------------------------- Assignee: Hany Mesha (was: Brian Stansberry) > Create an automated test for JBAS-2314 > -------------------------------------- > > Key: JBAS-2315 > URL: http://jira.jboss.com/jira/browse/JBAS-2315 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service > Reporter: Brian Stansberry > Assigned To: Hany Mesha > Priority: Minor > Fix For: JBossAS-4.2.1.CR1 > > > I currently test the JBAS-2314 fix manually; need to automate. Basically need to add a war to web-sso.ear that has secured resources but no authenticator configured. Test should access the normal sso test war on one server, then the other, and then on the 2nd server access the war w/o authenticator, confirming that no 403 is seen. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-1031) AdjListJDBCCacheLoaderConfig should not depend on JDBCCacheLoaderOld

by Galder Zamarreno (JIRA)

AdjListJDBCCacheLoaderConfig should not depend on JDBCCacheLoaderOld -------------------------------------------------------------------- Key: JBCACHE-1031 URL: http://jira.jboss.com/jira/browse/JBCACHE-1031 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.BETA2 Reporter: Galder Zamarreno Assigned To: Galder Zamarreno Priority: Minor Fix For: 2.0.0.CR1 AdjListJDBCCacheLoaderConfig, which is the base of the current JDBCCacheLoader configuration should not depend on the old cache loader implementation public AdjListJDBCCacheLoaderConfig() { setClassName(JDBCCacheLoaderOld.class.getName()); } /** * For use by {@link JDBCCacheLoaderOld}. * * @param base generic config object created by XML parsing. */ AdjListJDBCCacheLoaderConfig(IndividualCacheLoaderConfig base) { setClassName(JDBCCacheLoaderOld.class.getName()); populateFromBaseConfig(base); } -- 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, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-964) Optional 1.x marshalling for CacheLoaders using VersionAwareMarshaller

by Galder Zamarreno (JIRA)

Optional 1.x marshalling for CacheLoaders using VersionAwareMarshaller ---------------------------------------------------------------------- Key: JBCACHE-964 URL: http://jira.jboss.com/jira/browse/JBCACHE-964 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: Cache loaders Reporter: Galder Zamarreno Assigned To: Galder Zamarreno Priority: Minor Fix For: 2.0.0.BETA2, 2.0.0.GA Customers that want to use JBossCache 2.x might be reluctant to migrate their data from one format to the other. I can see how an existing customer might think this is a proper pain in the ass, independent of the benefits, and might reduce adoption among them. We want to remove barriers upgrading, but at the same time, we want new customer to use new marshalling, so I'd actually implement the possibility to use 1.x marshalling which is plan java serialization at the CacheLoader level. This could easily achieved adding a property to the <properties> section. The default in 2.x should be to use VAM and only people who are resilient to change their existing stores to VAM should use the 1.x option, which would need explicitly definition. This option also makes it easier for migration purpouses as customers should be able to start two cache instances with different cache loader marshalling method set. They could then loop through the first one using get operations and call put in the second instance. Just note that this does not apply to the marshalling done at replication level as there's no hard data that needs migrating. -- 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, 3 months

3
13
0 / 0

[JBoss JIRA] Created: (JBFORUMS-198) when I delete an user I have NullPointerException

by Luca Stancapiano (JIRA)

when I delete an user I have NullPointerException ------------------------------------------------- Key: JBFORUMS-198 URL: http://jira.jboss.com/jira/browse/JBFORUMS-198 Project: JBoss Forums Issue Type: Bug Components: Forum Model Layer Affects Versions: 1.2.0 Alpha Environment: any Reporter: Luca Stancapiano Assigned To: Ryszard Kozmik Fix For: 1.2.0 Alpha hi julien.......I tried to delete an user that is in posts of jboss forum.....after I deleted this user, if I click on posts where that user had posted I have NullPointerException I thought to correct this bug , using a UserNA object that implements User interface. This UserNA is used when I select the user from database and I haven't returned rows because user is deleted. In this case I add UserNA to User object of Post object. UserNA is declared in ForumPortlet object as final static , so the same object can to be used for each deleted user. What do you mean about it? I send you the patch -- 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, 3 months

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-4358) Fork a second notification listener from ListenerServiceMBeanSupport to get rid of handleNotification2

by Dimitris Andreadis (JIRA)

Fork a second notification listener from ListenerServiceMBeanSupport to get rid of handleNotification2 ------------------------------------------------------------------------------------------------------ Key: JBAS-4358 URL: http://jira.jboss.com/jira/browse/JBAS-4358 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: System service Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: JBossAS-4.2.1.CR1 A cleaner interface to support dynamic subscriptions would be to fork another notification listener, so that overriding handleNotification2(..) is not longer needed. In any case, maintain backwards compatibility. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Commented: (JASSIST-21) release javassist 3.1 to ibiblio

by Paul Gier (JIRA)

[ http://jira.jboss.com/jira/browse/JASSIST-21?page=comments#action_12360122 ] Paul Gier commented on JASSIST-21: ---------------------------------- It looks like version 3.1 has already been released to the central maven repository here: http://repo1.maven.org/maven2/jboss/javassist/ Versions 3.1, 3.3, and 3.4 are there so this issue can probably be closed. > release javassist 3.1 to ibiblio > -------------------------------- > > Key: JASSIST-21 > URL: http://jira.jboss.com/jira/browse/JASSIST-21 > Project: Javassist > Issue Type: Task > Environment: ibiblio.org/maven2 > Reporter: Jesse Kuhnert > > I have a project using javassist 3.1 and would find it easier to manage if the ibiblio/maven2 repo hosted javassist 3.1 (already has 3.0 > ) -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBBUILD-337) Change the JBoss Common Maven build scripts so that they use an inheritance model, and add JBossRetro

by Paul Gier (JIRA)

Change the JBoss Common Maven build scripts so that they use an inheritance model, and add JBossRetro ----------------------------------------------------------------------------------------------------- Key: JBBUILD-337 URL: http://jira.jboss.com/jira/browse/JBBUILD-337 Project: JBoss Build System Issue Type: Feature Request Components: Maven Reporter: Paul Gier Assigned To: Paul Gier The plugin configuration can be moved to the main build pom. Also the jar plugin should be changed to specify a minimum version of 2.1 so that the configuration parameters will always work. JBoss retro should also be called using the antrun plugin. -- 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, 3 months

2
2
0 / 0

[JBoss JIRA] Commented: (JBBUILD-158) Jar canonicalization and dependency isolation

by Paul Gier (JIRA)

[ http://jira.jboss.com/jira/browse/JBBUILD-158?page=comments#action_12360096 ] Paul Gier commented on JBBUILD-158: ----------------------------------- The maven assembly plugin can be used to package dependencies up with a project. It can extract and rejar the dependencies together with your project files. Is this something we want to do? > Jar canonicalization and dependency isolation > --------------------------------------------- > > Key: JBBUILD-158 > URL: http://jira.jboss.com/jira/browse/JBBUILD-158 > Project: JBoss Build System > Issue Type: Feature Request > Reporter: Scott M Stark > Assigned To: Paul Gier > Fix For: MavenBuild 2.0 > > > We need to look at the jar hell issue we have in terms of uneccessary dependencies and exposure of neccessary dependencies as something other than an implementation detail. Two tools in this space we should look at are: > genjar (http://genjar.sourceforge.net/) and jarjar (http://jarjar.sourceforge.net/). -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBBUILD-158) Jar canonicalization and dependency isolation

by Paul Gier (JIRA)

[ http://jira.jboss.com/jira/browse/JBBUILD-158?page=all ] Paul Gier updated JBBUILD-158: ------------------------------ Fix Version/s: MavenBuild 2.0 Associating this issue with Maven Build 2.0 project. > Jar canonicalization and dependency isolation > --------------------------------------------- > > Key: JBBUILD-158 > URL: http://jira.jboss.com/jira/browse/JBBUILD-158 > Project: JBoss Build System > Issue Type: Feature Request > Reporter: Scott M Stark > Assigned To: Paul Gier > Fix For: MavenBuild 2.0 > > > We need to look at the jar hell issue we have in terms of uneccessary dependencies and exposure of neccessary dependencies as something other than an implementation detail. Two tools in this space we should look at are: > genjar (http://genjar.sourceforge.net/) and jarjar (http://jarjar.sourceforge.net/). -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBBUILD-259) AOP pom

by Paul Gier (JIRA)

[ http://jira.jboss.com/jira/browse/JBBUILD-259?page=all ] Paul Gier updated JBBUILD-259: ------------------------------ Remaining Estimate: 3 days (was: 0 minutes) Description: Migrate AOP builds to maven. > AOP pom > ------- > > Key: JBBUILD-259 > URL: http://jira.jboss.com/jira/browse/JBBUILD-259 > Project: JBoss Build System > Issue Type: Sub-task > Components: Maven > Reporter: Ruel Loehr > Assigned To: Paul Gier > Fix For: MavenBuild 2.0 > > Time Spent: 1 day > Remaining Estimate: 3 days > > Migrate AOP builds to maven. -- 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, 3 months

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 April 2007