September 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3725) Specify DataSource settings at the application level (in the .EAR)

by raehalme (JIRA)

Specify DataSource settings at the application level (in the .EAR) ------------------------------------------------------------------ Key: JBAS-3725 URL: http://jira.jboss.com/jira/browse/JBAS-3725 Project: JBoss Application Server Issue Type: Patch Security Level: Public (Everyone can see) Components: CMP service Affects Versions: JBossAS-4.0.4.GA Reporter: raehalme Assigned To: Alexey Loubyansky At the moment you can specify application's DataSource settings either in the global JBoss configuration (standardjbosscmp-jdbc.xml) or in the EJB JAR (META-INF/jbosscmp-jdbc.xml). When developing EJB components that are re-used in many applications, it is frustrating to have to create a separate EJB JAR version for each application in order to be able to specify which DataSource to use for the EJB component. It would be much easier if the DataSource could be specified at the application level (in the EAR) because often all the application's EJB components use the same DataSource. In addition because the EJB JAR would no longer contain deployment specific settings, you could include the same EJB JAR file in all the application's EAR files. I propose that this improvement is implemented by reading default settings also from the EAR's META-INF/jbosscmp-jdbc.xml. You could then specify a default configuration for each application and still override it inside the EJB JAR if necessary. I have implemented this functionality using the source code from version 4.0.4.GA. I will attach the necessary patches to this issue for your evaluation. -- 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, 8 months

1
1
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-193) Enable configurable timeout on all calls of RpcServerCall.remoteInvoke(...)

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-193?page=all ] Ovidiu Feodorov closed JBMESSAGING-193. --------------------------------------- Resolution: Out of Date Refers to old code. > Enable configurable timeout on all calls of RpcServerCall.remoteInvoke(...) > --------------------------------------------------------------------------- > > Key: JBMESSAGING-193 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-193 > Project: JBoss Messaging > Issue Type: Feature Request > Components: Messaging Core Distributed Support > Affects Versions: 1.0.0 alpha PR3 > Reporter: Ovidiu Feodorov > Fix For: 1.2.0.Alpha1 > > > Client code currently lacks the possibility of administratively specify a timeout on RpcServerCall.remoteInvoke(...) calls. This is case for PeerSupport, QueuePeer and maybe others. Add the possibility to specify this timeout in a configuration 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3718) Unable to set Valid negative values for MBean attributes using Twiddle

by Sakthi Samabsivam (JIRA)

Unable to set Valid negative values for MBean attributes using Twiddle ------------------------------------------------------------------------- Key: JBAS-3718 URL: http://jira.jboss.com/jira/browse/JBAS-3718 Project: JBoss Application Server Issue Type: Patch Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-4.0.4.GA, JBossAS-4.0.4.CR2, JBossAS-4.0.3 SP1 Reporter: Sakthi Samabsivam Priority: Minor Fix For: JBossAS-4.0.5.GA When a customer tries to execute twiddle to set a negative value for one of the attributes, it throws the exception. For example when I try to set a Scheduler MBean InitialRepitions value to -1, it fails. Command: twiddle set "jboss:service=Scheduler" "InitialRepetitions" "-1". Possible problem might be, GetOpt class used in the org.jboss.console.twiddle.SetCommand Class is not accepting the -ve values.It consider the -ve numbers as an invalid option. -- 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, 8 months

2
4
0 / 0

[JBoss JIRA] Updated: (JBCACHE-680) TreeCache demo gui to update view instanteously

by Ben Wang (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-680?page=all ] Ben Wang updated JBCACHE-680: ----------------------------- Fix Version/s: 2.0.0 (was: 1.4.0) > TreeCache demo gui to update view instanteously > ----------------------------------------------- > > Key: JBCACHE-680 > URL: http://jira.jboss.com/jira/browse/JBCACHE-680 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Assigned To: Ben Wang > Priority: Minor > Fix For: 2.0.0, 1.4.0.SP2 > > > Previously the demo gui window has the onModify view change disabled becuase the potential deadlock when there is a tx scope and the Swing GUI view update is coming in from a different thread context. I can't reproduce this on 1.4 release now but to safeguard it, on the GUI side, I have used the getData() api to bypass the locking anyway. > Now, when I run the gui on PojoCache tutorial, it will have the field update automatically. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-680) TreeCache demo gui to update view instanteously

by Ben Wang (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-680?page=all ] Ben Wang updated JBCACHE-680: ----------------------------- Fix Version/s: 1.4.0.SP2 > TreeCache demo gui to update view instanteously > ----------------------------------------------- > > Key: JBCACHE-680 > URL: http://jira.jboss.com/jira/browse/JBCACHE-680 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Assigned To: Ben Wang > Priority: Minor > Fix For: 2.0.0, 1.4.0.SP2 > > > Previously the demo gui window has the onModify view change disabled becuase the potential deadlock when there is a tx scope and the Swing GUI view update is coming in from a different thread context. I can't reproduce this on 1.4 release now but to safeguard it, on the GUI side, I have used the getData() api to bypass the locking anyway. > Now, when I run the gui on PojoCache tutorial, it will have the field update automatically. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBSEAM-371) s:link does not propagate data model var

by Gavin King (JIRA)

s:link does not propagate data model var ---------------------------------------- Key: JBSEAM-371 URL: http://jira.jboss.com/jira/browse/JBSEAM-371 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Gavin King Assigned To: Gavin King Fix For: 1.1 When using h:commandLink and h:commandButton, you can use the iterator variable in the method binding expression. s:link should be the same. -- 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, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBSEAM-370) Default @Out scope to the component scope

by Gavin King (JIRA)

Default @Out scope to the component scope ----------------------------------------- Key: JBSEAM-370 URL: http://jira.jboss.com/jira/browse/JBSEAM-370 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Gavin King Assigned To: Gavin King Fix For: 1.1 Currently @Out defaults to EVENT scope for simple values that are not Seam components. For consistence with @DataModel, we should change to defaulting to the scope of the component which outjects the value. This is probably a better default anyway. Note that this is a breaking change, but best 'tis done now. -- 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, 8 months

1
1
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-407) XARecovery integration of JBossMessaging with JBossTS

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-407?page=all ] Ovidiu Feodorov updated JBMESSAGING-407: ---------------------------------------- Fix Version/s: 1.2.0.Alpha2 (was: 1.2.0.Alpha1) > XARecovery integration of JBossMessaging with JBossTS > ----------------------------------------------------- > > Key: JBMESSAGING-407 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-407 > Project: JBoss Messaging > Issue Type: Patch > Components: Tests and Performance > Environment: JBoss 4.0.3SP1, JBossTs 4.2GA, JBOSS Messagig 1.0.1CR2 > Reporter: Madhusudhan Konda > Assigned To: Ovidiu Feodorov > Fix For: 1.2.0.Alpha2 > > Attachments: artifacts.zip, jms-recovery-patch-all.txt, jms.zip, JMSProviderXAResourceRecovery.java, xa.zip, xarecovery-patch.txt, XATestStandaloneRecovery.java > > Original Estimate: 1 week > Remaining Estimate: 1 week > > To make JBossMessaging XAResource as recoverable using JBossTS RecoveryManager -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-518) Implement distributed destinations

by Tim Fox (JIRA)

Implement distributed destinations ---------------------------------- Key: JBMESSAGING-518 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-518 Project: JBoss Messaging Issue Type: Sub-task Reporter: Tim Fox Assigned To: Tim Fox -- 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, 8 months

2
2
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-289) Make service container configurable wrt datasource and persistence manager config

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-289?page=all ] Ovidiu Feodorov updated JBMESSAGING-289: ---------------------------------------- Fix Version/s: 1.2.0.Alpha2 (was: 1.2.0.Alpha1) > Make service container configurable wrt datasource and persistence manager config > --------------------------------------------------------------------------------- > > Key: JBMESSAGING-289 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-289 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Ovidiu Feodorov > Fix For: 1.2.0.Alpha2 > > > Must be made configurable so test suite can be run against different databases with different pm configs -- 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, 8 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 September 2006