December 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4763) Depends element in jboss-web.xml ignored

by Brian Stansberry (JIRA)

Depends element in jboss-web.xml ignored ---------------------------------------- Key: JBAS-4763 URL: http://jira.jboss.com/jira/browse/JBAS-4763 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment services Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Brian Stansberry Assigned To: Dimitris Andreadis Adding a depends element to jboss-web.xml seems to have no effect. Simplest way to confirm this is to add a jboss-web.xml with the following to deploy/ROOT.war/WEB-INF and start JBoss: <!DOCTYPE jboss-web PUBLIC "-//JBoss//DTD Web Application 5.0//EN" "http://www.jboss.org/j2ee/dtd/jboss-web_5_0.dtd"> <jboss-web> <depends>jboss:service=NonExistent</depends> </jboss-web> The ROOT.war deploys without issue even though the dependency is unresolved. -- 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

16 years, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1850) Test SSO Propagation from one browser window to second browser window

by Sohil Shah (JIRA)

Test SSO Propagation from one browser window to second browser window --------------------------------------------------------------------- Key: JBPORTAL-1850 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1850 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Identity Affects Versions: Identity-1.0, 2.6.2 Final, 2.6.3 Final Reporter: Sohil Shah Fix For: 2.6.4 Final Applies to both JOSSO and CAS integrations -- 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

16 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAOP-467) Serialize container proxies out of vm

by Kabir Khan (JIRA)

Serialize container proxies out of vm ------------------------------------- Key: JBAOP-467 URL: http://jira.jboss.com/jira/browse/JBAOP-467 Project: JBoss AOP Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.0.0.CR1 -- 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

16 years, 11 months

2
6
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1848) Portal CAS integration does not invalidate the CAS token

by Sohil Shah (JIRA)

Portal CAS integration does not invalidate the CAS token -------------------------------------------------------- Key: JBPORTAL-1848 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1848 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Identity Affects Versions: Identity-1.0, 2.6.2 Final Reporter: Sohil Shah Fix For: 2.6.4 Final, Identity-1.1 When a user logs out of Portal, the CAS token still stays alive and upon next Portal request, performs automatic authentication. End result is, user can never log out -- 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

16 years, 11 months

1
4
0 / 0

[JBoss JIRA] Created: (JBREM-799) Add a separate timeout parameter for callback clients, part 2

by Ron Sigal (JIRA)

Add a separate timeout parameter for callback clients, part 2 ------------------------------------------------------------- Key: JBREM-799 URL: http://jira.jboss.com/jira/browse/JBREM-799 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.4.0.Beta1 (Pinto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.4.0.Beta1 (Pinto) This issue is a continuation of JBREM-765 "Add a separate timeout parameter for callback clients". The changes have been applied to branches remoting_2_2_0_GA and remoting_2_x, but unit tests exist only for transports socket and bisocket. A unit test should be written for the RMI transport as well. However, no additional changes will be made to Remoting 2.2.2.GA, so this issue is introduced for 2.4.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

16 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBREM-851) In LeasePinger and TimerUtil replace Timer if it has shut down

by Ron Sigal (JIRA)

In LeasePinger and TimerUtil replace Timer if it has shut down -------------------------------------------------------------- Key: JBREM-851 URL: http://jira.jboss.com/jira/browse/JBREM-851 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.2.SP2, 2.2.2.GA_CP01, 2.4.0.Beta1 (Pinto) Reporter: Ron Sigal Fix For: 2.4.0.Beta1 (Pinto) When all of the TimerTasks running in a java.util.TimerTask have shut down, the TImer will also shut down, at which point it will accept no more TimerTasks. There are places in Remoting where there should be a test which will create a new Timer the attempt to schedule a TimerTask results in an exception. Two places the problem exists: 1. org.jboss.remoting.LeasePinger, and 2. org.jboss.remoting.util.TimerUtil. A similar problem is described in JBREM-748 "BisocketClientInvoker should guard agains scheduling on an expired Timer" Reported by James on Remoting forum. -- 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

16 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBREM-804) Enable HTTPClientInvoker to accept NO_THROW_ON_ERROR configuration by way of InvokerLocator

by Ron Sigal (JIRA)

Enable HTTPClientInvoker to accept NO_THROW_ON_ERROR configuration by way of InvokerLocator ------------------------------------------------------------------------------------------- Key: JBREM-804 URL: http://jira.jboss.com/jira/browse/JBREM-804 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.2.2.GA Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.4.0.Beta1 (Pinto) Currently, the value for the parameter org.jboss.remoting.transport.http.HTTPMetadataConstants.NO_THROW_ON_ERROR in org.jboss.remoting.transport.http.HTTPClientInvoker is configurable only by way of the invocation metadata map passed to org.jboss.remoting.Client.invoke(). However, for EJB3 invocations, the Client is created by the EJB3 proxy (org.jboss.aspects.remoting.InvokeRemoteInterceptor, in particular) and is not accessible by application code. If HTTPClientInvoker checked the InvokerLocator for this parameter, then it could be configured declaratively in the EJB3 jboss-service.xml file. -- 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

16 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-4943) jboss-ds_1_5.dtd is wrong

by Michael Lipp (JIRA)

jboss-ds_1_5.dtd is wrong ------------------------- Key: JBAS-4943 URL: http://jira.jboss.com/jira/browse/JBAS-4943 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation, JCA service Affects Versions: JBossAS-4.0.5.GA Environment: Any Reporter: Michael Lipp Assigned To: Norman Richards The jboss-ds_1_5.dtd (as distributed in docs/dtd/) is wrong or not up-to-date (and there is no newer version and no out-of-date mark). As has been pointed out by Adrian Brock in JBAS-4942, it is possible to specify a loader-repository like this: <connection-factories>  <loader-repository>jboss.test:loader=JavaClassIsolation</loader-repository> <tx-connection-factory>  <rar-name>some.ear#some.rar</rar-name> <etc/> </tx-connection-factory> </connection-factories> ... although this is not compliant with the DTD! Keeping the DTD up-to-date would avoid unnecessary bug reports and/or forum questions because looking at the DTD is the first step in finding out how to configure required behavior. -- 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

16 years, 11 months

5
7
0 / 0

[JBoss JIRA] Created: (JBAS-4842) TECH REVIEW: Server Configuration Guide - TRACKER

by samson kittoli (JIRA)

TECH REVIEW: Server Configuration Guide - TRACKER -------------------------------------------------- Key: JBAS-4842 URL: http://jira.jboss.com/jira/browse/JBAS-4842 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Server Configuration Guide Affects Versions: JBossAS-4.2.2.GA Reporter: samson kittoli -- 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

16 years, 11 months

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-4819) TECH REVIEW: Installation Guide - TRACKER

by Michael Smith (JIRA)

TECH REVIEW: Installation Guide - TRACKER ----------------------------------------- Key: JBAS-4819 URL: http://jira.jboss.com/jira/browse/JBAS-4819 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Installation Guide Affects Versions: JBossAS-4.2.2.GA Reporter: Michael Smith Tracker for Chapter Edits of the Installation Guide -- 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

16 years, 11 months

4
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2007