December 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-595) can't create rules with a space in the name

by Michael Neale (JIRA)

can't create rules with a space in the name ------------------------------------------- Key: JBRULES-595 URL: http://jira.jboss.com/jira/browse/JBRULES-595 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale Fix For: 3.1-m1 -- 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, 7 months

1
1
0 / 0

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

by Pavel Tsekov (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1768?page=comments#action_12349320 ] Pavel Tsekov commented on JBAS-1768: ------------------------------------ Adrian, do you mean that some of the tests in the JBossAS testsuite are by other projects as well ? If this is true - am I correctly interpreting you comment that you want those common tests moved to a separate project (cvs/svn module) so that everyone who depends on them can use them in a clean way and share the same codebase ? > 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 > Assigned To: Pavel Tsekov > Fix For: JBossAS-4.2.1.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

19 years, 7 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-1770) Enabling the testsuite to be used by users

by Pavel Tsekov (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1770?page=comments#action_12349319 ] Pavel Tsekov commented on JBAS-1770: ------------------------------------ What are the immediate requirements for this task ? Is it correct to consider altering the build/packaging process to include the testsuite and its dependencies into the distribution as the primary objective ? Which of the enhancements above are required and which should be added to the wish list ? Do we have to include some kind of documentation about the details on running the different tests ? Those questions might seem stupid to you but, please, bear with me since I am a newcomer and it is not obvious for me. > Enabling the testsuite to be used by users > ------------------------------------------ > > Key: JBAS-1770 > URL: http://jira.jboss.com/jira/browse/JBAS-1770 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Test Suite > Reporter: Adrian Brock > Assigned To: Pavel Tsekov > > The testsuite should be available for users to use. > e.g. by including it in JBOSS_DIST/client or JBOSS_DIST/test??? > Other enhancements might include: > * Using JSR88 for deployment > * Using JSR160 for the MBeanServerConnection > * Exposing functionality available on the admin console > To help users provide better bug reports we should also > provide skeleton tests that the user can "extend". -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPORTAL-372) Basic Publish Approval Workflow

by Sohil Shah (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-372?page=all ] Sohil Shah resolved JBPORTAL-372. --------------------------------- Resolution: Done > Basic Publish Approval Workflow > ------------------------------- > > Key: JBPORTAL-372 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-372 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Portal CMS > Affects Versions: 2.6 Final > Reporter: James Williams > Assigned To: Sohil Shah > Priority: Minor > Fix For: 2.6.Alpha1 > > > Optional feature which mandates that content changes must flow through a simple approval process that involves a Publisher and one or more Managers. Once the publisher makes a content change an email approval request should be sent to the manager list. The content change will not be made available to readers until all Managers approve 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

19 years, 7 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPORTAL-931) jBPM Integration for CMS

by Sohil Shah (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-931?page=all ] Sohil Shah resolved JBPORTAL-931. --------------------------------- Resolution: Done > jBPM Integration for CMS > ------------------------ > > Key: JBPORTAL-931 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-931 > Project: JBoss Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Portal CMS > Affects Versions: 2.6 Final > Reporter: Roy Russo > Assigned To: Sohil Shah > Fix For: 2.6.Alpha1 > > -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-672) Server side valve

by Ovidiu Feodorov (JIRA)

Server side valve ----------------- Key: JBMESSAGING-672 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-672 Project: JBoss Messaging Issue Type: Sub-task Components: JMS Clustering Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Critical Fix For: 1.2.0.Beta1 -- 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, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-3955) Upgrade commons-httpclient to v3.0.1

by Dimitris Andreadis (JIRA)

Upgrade commons-httpclient to v3.0.1 ------------------------------------ Key: JBAS-3955 URL: http://jira.jboss.com/jira/browse/JBAS-3955 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Other Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: JBossAS-4.2.0.CR1 Utilize the same version needed by JBoss Portal. -- 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, 7 months

1
3
0 / 0

[JBoss JIRA] Created: (JBPM-812) pluggable persistence

by Gavin King (JIRA)

pluggable persistence --------------------- Key: JBPM-812 URL: http://jira.jboss.com/jira/browse/JBPM-812 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Reporter: Gavin King Assigned To: Tom Baeyens Currently jBPM likes to own and manage its own persistence context. This sucks, especially for Seam. I want to be able to pass it an existing Hibernate Session, or JPA EM, and have it use that. -- 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, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-810) Actions that validate transitions

by Gavin King (JIRA)

Actions that validate transitions --------------------------------- Key: JBPM-810 URL: http://jira.jboss.com/jira/browse/JBPM-810 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Reporter: Gavin King Assigned To: Tom Baeyens It is useful to be able to have an action in the stack of actions for a transition "cancel" the transition: <transition name="delete"> <action expression="#{user.checkDeletePermission}"/> <action expression="#{document.delete}"/> </transition> The first action can cancel execution of the transition (and shortcircuit the rest of the action stack) by something like: * returning false? * throwing a predefined exception class CancelTransitionException? Or perhaps we could have a specific concept of a Validator: <transition name="delete"> <validator expression="#{user.admin}"/> <action expression="#{document.delete}"/> </transition> jBPM could have a Validator interface, and the Seam integration would just let you use an EL, and check the boolean return value. -- 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, 7 months

2
1
0 / 0

[JBoss JIRA] Updated: (JBPM-653) make the process parent classloader configurable

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-653?page=all ] Tom Baeyens updated JBPM-653: ----------------------------- Fix Version/s: jBPM 3.2 beta 1 (was: jBPM 3.2 alpha 3) > make the process parent classloader configurable > ------------------------------------------------ > > Key: JBPM-653 > URL: http://jira.jboss.com/jira/browse/JBPM-653 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Fix For: jBPM 3.2 beta 1 > > > now, always the jBPM classloader is taken as a parent for the process classloaders. this should be made configurable. at least one other possibility should be to configure the context classloader. -- 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, 7 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 December 2006