November 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3789) Update JBossORG-EULA.txt

by Dimitris Andreadis (JIRA)

Update JBossORG-EULA.txt ------------------------ Key: JBAS-3789 URL: http://jira.jboss.com/jira/browse/JBAS-3789 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Build System Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: JBossAS-4.0.6.CR1, JBossAS-4.0.5.GA Attachments: JBossORG-EULA.txt Use the correct EULA in the jboss distribution. -- 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, 6 months

1
9
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-152) Cannot unregister membership listener

by Tamas Barta (JIRA)

Cannot unregister membership listener ------------------------------------- Key: JBCLUSTER-152 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-152 Project: JBoss Clustering Issue Type: Bug Security Level: Public (Everyone can see) Environment: Doesn't matter Reporter: Tamas Barta Assigned To: Brian Stansberry org.jboss.ha.framework.server.HAPartitiomImpl.java: public void unregisterMembershipListener(HAMembershipListener listener) { boolean isAsynch = (this.allowSyncListeners == false) || (listener instanceof AsynchHAMembershipListener) || (listener instanceof AsynchHAMembershipExtendedListener); if( isAsynch ) { synchronized(this.asynchListeners) { this.asynchListeners.add(listener); } } else { synchronized(this.synchListeners) { this.synchListeners.add(listener); } } } "synchListeners.add" should be "synchListeners.remove" -- 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, 6 months

2
1
0 / 0

[JBoss JIRA] Updated: (JBAS-1824) JACC: <role-name>*</role-name> in web.xml

by Anil Saldhana (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1824?page=all ] Anil Saldhana updated JBAS-1824: -------------------------------- Original Estimate: 4 hours (was: 1 hour) Remaining Estimate: 4 hours (was: 1 hour) Fix Version/s: JBossAS-4.2.0.CR1 JBossAS-4.0.5.SP1 Assignee: Anil Saldhana (was: Scott M Stark) Complexity: Medium Scheduling the configurable feature of WebResourcePermission("/any/*", null) approach, for the next release of JBoss 4.0.x. > JACC: <role-name>*</role-name> in web.xml > ----------------------------------------- > > Key: JBAS-1824 > URL: http://jira.jboss.com/jira/browse/JBAS-1824 > Project: JBoss Application Server > Issue Type: Feature Request > Components: Security > Affects Versions: JBossAS-4.0.2 Final > Environment: - > Reporter: Roland R?z > Assigned To: Anil Saldhana > Priority: Minor > Fix For: JBossAS-4.2.0.CR1, JBossAS-4.0.5.SP1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > In some cases I wish to do authentication without authorisation. For example everybody has access to my web-resource, but I want to know who she/he is. > Therefore the accessing user must login. > So my web.xml contains the following snippet: > ... > <security-constraint> > <web-resource-collection> > <web-resource-name>Protected Helloworld example</web-resource-name> > <description/> > <url-pattern>/servlet/HelloWorldExample</url-pattern> > <http-method>POST</http-method> > <http-method>GET</http-method> > </web-resource-collection> > <auth-constraint> > <role-name>*</role-name> > </auth-constraint> > </security-constraint> > <login-config> > <auth-method>BASIC</auth-method> > <realm-name>public</realm-name> > </login-config> > ... > The web app runs with this configuration in Tomcat 5.5.8 standalone but not in Jboss. > To run it in Jboss I have to add the following element: > <security-role> > <role-name>aRole</role-name> > </security-role> > The JACC spec (section 3.1.3.1, paragraph 3)states : > " ?. When an auth-constraint names the reserved role-name, "*", all of the patterns in the containing security-constraint must be combined with all of the roles defined in the web application." > JBoss implemented this by combining all of the patterns with all roles defined in the web.xml and assumes that each role has to be defined in the web.xml. > But the web applications roles are probably defined in other files than the web.xml. In our case we use JACC with an external authentication provider. And each time, the roles changes, I also would have to modify the web.xml. > It is desirable if the auth-contraint with the role-name "*" acceppts "all" roles and not only those that are defined in the web.xml. > Or is this a JACC spec issue? > Regards, > Andrea -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-777) Business interface on super classes

by Carlo de Wolf (JIRA)

Business interface on super classes ----------------------------------- Key: EJBTHREE-777 URL: http://jira.jboss.com/jira/browse/EJBTHREE-777 Project: EJB 3.0 Issue Type: Feature Request Affects Versions: EJB 3.0 RC9 - FD Reporter: Carlo de Wolf Priority: Minor Note that this is contradictory to the specs. EJB3 4.6.2 4th bullet: The class must implement the bean's business interface(s) or the methods of the bean's business interface(s), if any. There is nothing said about super classes. If it breaks TCK, reject it. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3831) The cookie containing the JSESSIONID is missing when the JVMRoute has to be changed.

by Jean-Frederic Clere (JIRA)

The cookie containing the JSESSIONID is missing when the JVMRoute has to be changed. ------------------------------------------------------------------------------------ Key: JBAS-3831 URL: http://jira.jboss.com/jira/browse/JBAS-3831 Project: JBoss Application Server Issue Type: Support Patch Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-4.0.1 SP1 Reporter: Jean-Frederic Clere Assigned To: Jean-Frederic Clere Priority: Minor See http://jira.jboss.com/jira/browse/JBAS-3829 -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3830) [Entity Container] Could not restore ejb timers

by G??tz Boesler (JIRA)

[Entity Container] Could not restore ejb timers ----------------------------------------------- Key: JBAS-3830 URL: http://jira.jboss.com/jira/browse/JBAS-3830 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.5.GA Environment: XP Reporter: G??tz Boesler Deploying the application causes an "Could not restore eje timers" error. The application runs in 4.04 without problems. -- 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, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPM-774) Add JBoss EULA

by Rajesh Rajasekaran (JIRA)

Add JBoss EULA -------------- Key: JBPM-774 URL: http://jira.jboss.com/jira/browse/JBPM-774 Project: JBoss jBPM Issue Type: Feature Request Reporter: Rajesh Rajasekaran Assigned To: Tom Baeyens Fix For: jBPM 3.1.4 Attachments: JBossORG-EULA.txt Attached is the JBossORG-EULA.txt 1. The eula should be checked into the project's source tree. 2. The project's build should include the EULA in project distributables, ie, whatever is the unit of publish: zip, tgz, 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, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBREM-605) Inform a server side listener that a callback has been delivered.

by Ron Sigal (JIRA)

Inform a server side listener that a callback has been delivered. ----------------------------------------------------------------- Key: JBREM-605 URL: http://jira.jboss.com/jira/browse/JBREM-605 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Beta1 (Bluto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.2.0.Beta1 (Bluto) JBossMessaging has a need to know that a Callback has been pulled to the client side and has been processed. See JBMESSAGING-207 for some discussion. -- 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, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JBREM-601) Integrate http with messaging

by Ron Sigal (JIRA)

Integrate http with messaging ----------------------------- Key: JBREM-601 URL: http://jira.jboss.com/jira/browse/JBREM-601 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Beta1 (Bluto) Reporter: Ron Sigal Assigned To: Tom Elrod Fix For: 2.2.0.Beta1 (Bluto) A few changes need to be made for the http transport to work with JBossMessaging. -- 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, 6 months

2
2
0 / 0

[JBoss JIRA] Resolved: (JASSIST-20) Proxy serialization

by Shigeru Chiba (JIRA)

[ http://jira.jboss.com/jira/browse/JASSIST-20?page=all ] Shigeru Chiba resolved JASSIST-20. ---------------------------------- Resolution: Done I have fixed this. > Proxy serialization > ------------------- > > Key: JASSIST-20 > URL: http://jira.jboss.com/jira/browse/JASSIST-20 > Project: Javassist > Issue Type: Feature Request > Reporter: Carlo de Wolf > Assigned To: Shigeru Chiba > Attachments: JASSIST-20.zip > > > Proxy serialization doesn't work accross VM's (/ ClassLoaders). -- 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, 6 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 November 2006