October 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBSEAM-161) Calendaring/scheduling

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-161?page=all ] Gavin King updated JBSEAM-161: ------------------------------ Fix Version/s: (was: 1.1) Priority: Major (was: Critical) We have now made significant progress on this area. However, there is still no integration of Quartz, or of jBPM business calendars. > Calendaring/scheduling > ---------------------- > > Key: JBSEAM-161 > URL: http://jira.jboss.com/jira/browse/JBSEAM-161 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Reporter: Gavin King > Assigned To: Gavin King > > We need calendared events to be processed in the scope of a Seam context. > We need to investigate what timer solutions make sense: jBPM, Quartz, EJB timers? -- 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

18 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBSEAM-378) Add an infrastructure component for Accessing a JBoss mail session

by Bradley Smith (JIRA)

Add an infrastructure component for Accessing a JBoss mail session ------------------------------------------------------------------ Key: JBSEAM-378 URL: http://jira.jboss.com/jira/browse/JBSEAM-378 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Bradley Smith Priority: Minor Please add an infrastructure component for interacting with a javax.mail.session obtained from JNDI. possible component name: org.jboss.seam.core.mail -- 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

18 years, 3 months

2
1
0 / 0

[JBoss JIRA] Closed: (JBSEAM-184) Async EJB support

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-184?page=all ] Gavin King closed JBSEAM-184. ----------------------------- Fix Version/s: 1.1 Resolution: Done > Async EJB support > ----------------- > > Key: JBSEAM-184 > URL: http://jira.jboss.com/jira/browse/JBSEAM-184 > Project: JBoss Seam > Issue Type: Feature Request > Components: EJB3 > Reporter: Gavin King > Assigned To: Gavin King > Fix For: 1.1 > > > Currently, I can't have a Seam component that is an EJB3 with methods called asynchronously. Perhaps this makes no sense (the AJAX case is handle-able just be a multithreaded SFSB). But I need to think this through properly. -- 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

18 years, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBSEAM-211) Async processing of Seam events

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-211?page=all ] Gavin King closed JBSEAM-211. ----------------------------- Fix Version/s: 1.1 Resolution: Done Done using Timer service > Async processing of Seam events > ------------------------------- > > Key: JBSEAM-211 > URL: http://jira.jboss.com/jira/browse/JBSEAM-211 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Affects Versions: 1.0 > Reporter: Gavin King > Assigned To: Gavin King > Fix For: 1.1 > > > The Seam event bus should be enhanced to allow event processing via a Queue or Topic. This will require some major changes... -- 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

18 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-732) Security Domain Manager for lookup of Security Managers(Auth/authorizn mgr)

by Anil Saldhana (JIRA)

Security Domain Manager for lookup of Security Managers(Auth/authorizn mgr) --------------------------------------------------------------------------- Key: EJBTHREE-732 URL: http://jira.jboss.com/jira/browse/EJBTHREE-732 Project: EJB 3.0 Issue Type: Task Components: Security Affects Versions: EJB 3.0 RC9 - FD Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: EJB 3.0 RC10 - FD There is a need to consolidate the lookup of a SubjectSecurityManager (AuthenticationManager + RealmMapping) interfaces to a single class. -- 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

18 years, 3 months

1
1
0 / 0

[JBoss JIRA] Assigned: (JBAS-1768) Isolating the test harness

by Ryan Campbell (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1768?page=all ] Ryan Campbell reassigned JBAS-1768: ----------------------------------- Assignee: (was: Rajesh Rajasekaran) > Isolating the test harness > -------------------------- > > Key: JBAS-1768 > URL: http://jira.jboss.com/jira/browse/JBAS-1768 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Test Suite > Affects Versions: JBossAS-4.0.1 Final, JBossAS-4.0.2RC1, JBossAS-4.0.1 SP1 > Reporter: Adrian Brock > Fix For: JBossAS-4.0.6.CR1 > > > Since some projects are already using the test harness > org.jboss.test (from the testsuite) > this needs to be isolated to break the circular build dependency. > Additionally, we should look at making this available to users > 1) For their own use > 2) When reporting 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

18 years, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-401) Release 1.0.1 GA after waiting for a week for feedback on the latest CR

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-401?page=all ] Ovidiu Feodorov closed JBMESSAGING-401. --------------------------------------- Resolution: Done > Release 1.0.1 GA after waiting for a week for feedback on the latest CR > ----------------------------------------------------------------------- > > Key: JBMESSAGING-401 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-401 > Project: JBoss Messaging > Issue Type: Task > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Fix For: 1.0.1.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

18 years, 3 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAS-2909) Testcase infra structure for MemoryLeaks

by Ryan Campbell (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2909?page=all ] Ryan Campbell reassigned JBAS-2909: ----------------------------------- Assignee: (was: Rajesh Rajasekaran) > Testcase infra structure for MemoryLeaks > ---------------------------------------- > > Key: JBAS-2909 > URL: http://jira.jboss.com/jira/browse/JBAS-2909 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Clebert Suconic > Fix For: JBossAS-4.0.6.CR1, JBossAS-5.0.1.CR1 > > > We could modify JBossTestCase::deploy to introspect every package being deployed and write details to a list. (say the name of the loaded classes, the name of the package and the name of the test). > Later before stopping the server on the testsuite, we should introspect loaded classes on the server and compare to the list. The intersection should be zero. > Also before doing such comparisson is a good idea to force an OutOfMemoryError, forcing eventual SoftReferences being released (e.g. JavaSerialization or any other Reflection cache) > To load the list we could use -XX:PrintClassHIstogram with a kill -3 on the server, or JVMTIInterface from JBossProfiler could also give you such list (by using a couple of methods for that). > This is an example of how to list loaded classes using JVMTIInterface from JBossProfiler: > jvmtiInterface.forceReleaseOfGC(); > Class[] classes = jvmtiInterface.getLoadedClasses(); -- 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

18 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3748) give run.sh the ability to run the VM in background and export the PID as an env. var.

by John Mazzitelli (JIRA)

give run.sh the ability to run the VM in background and export the PID as an env. var. -------------------------------------------------------------------------------------- Key: JBAS-3748 URL: http://jira.jboss.com/jira/browse/JBAS-3748 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.5.CR1 Reporter: John Mazzitelli Assigned To: Dimitris Andreadis Fix For: JBossAS-4.0.5.GA Attachments: patch.txt I want to write an init.d script with the typical start - stop options to start JBossAS. I want to use the method of writing a pid file when started and killing the pid found in the file when stopping. I do not want to use the "normal" shutdown mechanism to stop it because that assumes the JBoss instance has exposed its remote MBean interface (and I do not want to assume that). Plus, I want to ensure it is killed, and using the "kill" command is as fool-proof as I need it to be. I also want to be able to use run.sh to start the instance (I do not want to have to do all the work run.sh does - setting up the JVM, passing in arguments, worrying about all the cygwin - darwin things, etc. etc.). But, if my init.d script starts run.sh, I cannot use $! in my init.d script as the pid file contents because $! is the pid of run.sh script process. It is NOT the pid of the JBoss JVM instance itself. If I then go to kill the run.sh process, it dies, but the JVM process does not. Therefore, the init.d stop option does not work - it cannot stop the JBoss VM. I would like to propose to make the following change to run.sh that would facilitate this. This change is backwards compatible. What this change does is - if I set the environment variable "LAUNCH_JBOSS_IN_BACKGROUND" and source run.sh, run.sh will export JBOSS_PID as the pid value of the JVM process. My init.d script (the thing that sources run.sh) will be able to write JBOSS_PID anywhere I want and thus later be able to use it to kill the JBoss VM. See attached patch for the change. -- 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

18 years, 3 months

3
12
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-573) Add clustering crash and recovery tests to suite

by Tim Fox (JIRA)

Add clustering crash and recovery tests to suite ------------------------------------------------ Key: JBMESSAGING-573 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-573 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.0.Alpha2 -- 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

18 years, 3 months

1
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2006