September 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-713) META-INF/jboss-service.xml doesn't apply to POJO service bean (ie. allow to configure POJO service bean attributes at deployment time)

by Wenbo Zhu (JIRA)

META-INF/jboss-service.xml doesn't apply to POJO service bean (ie. allow to configure POJO service bean attributes at deployment time) --------------------------------------------------------------------------------------------------------------------------------------- Key: EJBTHREE-713 URL: http://jira.jboss.com/jira/browse/EJBTHREE-713 Project: EJB 3.0 Issue Type: Bug Components: EJB3 Extensions Affects Versions: EJB 3.0 RC7 - FD Environment: JBoss App Server 4.0.4 GA release. Reporter: Wenbo Zhu META-INF/jboss-service.xml is not used when deploying POJO service bean. Also, the EJB3 guide examples contain a dummy jboss-service.xml under META-INF, which should be cleaned up (if not supported). As this is not part of ejb3 standards, it could be just a feature request - to allow using descriptor file for configuring mbean attrs. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1052) Build taking too long and moving too many files around.

by Roy Russo (JIRA)

Build taking too long and moving too many files around. ------------------------------------------------------- Key: JBPORTAL-1052 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1052 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6.Alpha1 Reporter: Roy Russo Assigned To: Roy Russo Fix For: 2.6.Alpha1 a 5 minute build is not necessary! -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] Commented: (JBPM-288) Fork/Join and child token deactivation

by Britt Miner (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-288?page=comments#action_12343762 ] Britt Miner commented on JBPM-288: ---------------------------------- For anyone experiencing this problem, I've posted a work-around here http://wiki.jboss.org/wiki/Wiki.jsp?page=Jbpm_EndForkedTokensAH. > Fork/Join and child token deactivation > -------------------------------------- > > Key: JBPM-288 > URL: http://jira.jboss.com/jira/browse/JBPM-288 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.0 > Environment: Any > Reporter: Lukasz Czekierda > Assigned To: Tom Baeyens > Attachments: processdefinition.xml, SimpleProcessTest.java > > > Join implementation has incorrectly/no implemented activation of finished child tokens. They remain active till the end of the whole process. Example from junit test (Wfp03SynchronizationTest.testSynchronizationFirstTokenFirst) works perfectly as long as is unmodified. After adding a few bottom lines and changing a transition in join I get my error. Token.end is called on children and the root token in the LAST state, when finishing the entire process. When in stateX or stateY, the process still reports two active child tokens. > --- > "<process-definition>" + > " <start-state name='start'>" + > " <transition to='fork' />" + > " </start-state>" + > " <fork name='fork'>" + > " <transition name='first' to='one' />" + > " <transition name='second' to='two' />" + > " </fork>" + > " <state name='one'>" + > " <transition to='join' />" + > " </state>" + > " <state name='two'>" + > " <transition to='join' />" + > " </state>" + > " <join name='join'>" + > " <transition to='stateX' />" + > " </join>" + > " <state name='stateX'>" + > " <transition to='stateY' />" + > " </state>" + > " <state name='stateY'>" + > " <transition to='end' />" + > " </state>" + > " <end-state name='end' />" + > "</process-definition>" -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPTL-51) Have a different page to change password

by Thomas Heute (JIRA)

[ http://jira.jboss.com/jira/browse/JBPTL-51?page=all ] Thomas Heute updated JBPTL-51: ------------------------------ Attachment: JBPTL-51.zip Contribution of Benjamin Lerer Thanks ! > Have a different page to change password > ---------------------------------------- > > Key: JBPTL-51 > URL: http://jira.jboss.com/jira/browse/JBPTL-51 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Portal Core > Reporter: Thomas Heute > Priority: Optional > Attachments: JBPTL-51.zip > > Original Estimate: 1 hour, 30 minutes > Remaining Estimate: 1 hour, 30 minutes > > Just to make it more convenient, a different page (than the edit profile page) to change the password would be nice. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-753) Leaving a Superstate does not record a NodeLog

by Britt Miner (JIRA)

Leaving a Superstate does not record a NodeLog ---------------------------------------------- Key: JBPM-753 URL: http://jira.jboss.com/jira/browse/JBPM-753 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM 3.1.2 Reporter: Britt Miner Assigned To: Tom Baeyens Leaving a Superstate should persist a NodeLog, but doesn't. -- 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, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-136) Define a set of EPRs for the Email, Ftp and Database.

by Arvinder Singh (JIRA)

Define a set of EPRs for the Email, Ftp and Database. ----------------------------------------------------- Key: JBESB-136 URL: http://jira.jboss.com/jira/browse/JBESB-136 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: ESB Core Reporter: Arvinder Singh Assigned To: Arvinder Singh Fix For: 4.0 Define a set of EPRs for the Email, Ftp and Database. -- 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, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (JBCOMMON-9) Remote the dom4j dependency from org.jboss.util.state.xml.StateMachineParser

by Dimitris Andreadis (JIRA)

Remote the dom4j dependency from org.jboss.util.state.xml.StateMachineParser ---------------------------------------------------------------------------- Key: JBCOMMON-9 URL: http://jira.jboss.com/jira/browse/JBCOMMON-9 Project: JBoss Common Issue Type: Task Security Level: Public (Everyone can see) Components: core Affects Versions: 1.0.0.CR1 Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: 2.0.0.Beta, 1.0.0.GA StateMachineParser is the only class in the common package that has a dependency on dom4j. Re-write it so the dom4j dependency is removed. -- 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, 10 months

1
2
0 / 0

[JBoss JIRA] Commented: (JBAS-3652) Add EULA to licenses folder of distribution

by Rajesh Rajasekaran (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3652?page=comments#action_12343741 ] Rajesh Rajasekaran commented on JBAS-3652: ------------------------------------------ Will get this in today. > Add EULA to licenses folder of distribution > ------------------------------------------- > > Key: JBAS-3652 > URL: http://jira.jboss.com/jira/browse/JBAS-3652 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Ryan Campbell > Assigned To: Rajesh Rajasekaran > Priority: Critical > Fix For: JBossAS-4.0.5.GA > > Attachments: JBossEULA.doc, JBossEULA.pdf, JBossEULA.txt > > > We need to include the attached EULA text file in all "licenses" folders of > our distributions. It is an umbrella EULA that does not change the > fact that our source code is open source...it simply applies a little more > rigor around use of trademarks and logos as well as Export conditions. > We do not need to retrofit this into existing builds, just new builds on an > ongoing basis. Ex. JBoss AS 4.0.5 should include 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, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-3652) Add EULA to licenses folder of distribution

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3652?page=comments#action_12343739 ] Dimitris Andreadis commented on JBAS-3652: ------------------------------------------ Rajesh, working on this? > Add EULA to licenses folder of distribution > ------------------------------------------- > > Key: JBAS-3652 > URL: http://jira.jboss.com/jira/browse/JBAS-3652 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Ryan Campbell > Assigned To: Rajesh Rajasekaran > Priority: Critical > Fix For: JBossAS-4.0.5.GA > > Attachments: JBossEULA.doc, JBossEULA.pdf, JBossEULA.txt > > > We need to include the attached EULA text file in all "licenses" folders of > our distributions. It is an umbrella EULA that does not change the > fact that our source code is open source...it simply applies a little more > rigor around use of trademarks and logos as well as Export conditions. > We do not need to retrofit this into existing builds, just new builds on an > ongoing basis. Ex. JBoss AS 4.0.5 should include 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3554) Upgrade JBoss AS to use MyFaces 1.1.4

by Dimitris Andreadis (JIRA)

Upgrade JBoss AS to use MyFaces 1.1.4 ------------------------------------- Key: JBAS-3554 URL: http://jira.jboss.com/jira/browse/JBAS-3554 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Dimitris Andreadis Fix For: JBossAS-5.0.0.Beta, JBossAS-4.0.5.GA Need to upgrade to MyFaces 1.1.4 when it gets released. This should fix the problem of not saving server-side state: http://issues.apache.org/jira/browse/MYFACES-1296 -- 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, 10 months

2
10
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