August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-995) make forums work with 2.4

by Boleslaw Dawidowicz (JIRA)

make forums work with 2.4 ------------------------- Key: JBPORTAL-995 URL: http://jira.jboss.com/jira/browse/JBPORTAL-995 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Forums Affects Versions: 2.4 Final Reporter: Boleslaw Dawidowicz Assigned To: Boleslaw Dawidowicz Fix For: 2.4 Final make forums inside of portal codebase compile and work ok with latest 2.4 -- 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, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-739) isSuspended() incorrectly reflects state immediately after suspension

by Ryan Campbell (JIRA)

isSuspended() incorrectly reflects state immediately after suspension --------------------------------------------------------------------- Key: JBPM-739 URL: http://jira.jboss.com/jira/browse/JBPM-739 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM 3.1.1 Reporter: Ryan Campbell Assigned To: Tom Baeyens instance.isSuspended() doesn't reflect suspended state if you have just suspsended an instance, only if you are reloading it from the DB. -- 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, 11 months

3
2
0 / 0

[JBoss JIRA] Resolved: (JBAS-3306) Upgrade JBoss AS to use MyFaces 1.1.3

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3306?page=all ] Dimitris Andreadis resolved JBAS-3306. -------------------------------------- Resolution: Done Consider this closed. We'll update to MyFaces 1.1.4 when it gets released. See the linked JBAS-3554. > Upgrade JBoss AS to use MyFaces 1.1.3 > ------------------------------------- > > Key: JBAS-3306 > URL: http://jira.jboss.com/jira/browse/JBAS-3306 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: JBossAS-4.0.4.GA > Reporter: Gavin King > Assigned To: Stan Silvert > Priority: Critical > Fix For: JBossAS-4.0.5.CR1 > > > We need to upgrade JBoss to use MyFaces 1.1.3, which fixes many bugs. This is critical priority for Seam. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3553) Failover 'java.naming.provider.url' entries

by Andy Brook (JIRA)

Failover 'java.naming.provider.url' entries ------------------------------------------- Key: JBAS-3553 URL: http://jira.jboss.com/jira/browse/JBAS-3553 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-4.0.4.GA Environment: Linux, Debian (Ubuntu 6.0.6). LDAP server is M$ Active Directory Reporter: Andy Brook Assigned To: Scott M Stark We have a corporate net with multiple DC servers each acting as failovers for eachother. I have to pick one as the naming provider in the LDAP LoginModules login-config.xml section. A recent outage identified a weakness in this approach, the server was turned off and all applicaitons went offline. I would like to suggest a bunch of alternate naming providers that can be used if the main one goes offline. I've just implemented this to address the problem but have yet to test it extensively. Its not a complex fix, I just pull out <module-option name="java.naming.provider.url.backups">abc|def</module-option> tags. I check the availability of the given server at login module initialisation. I havent figured out whether this is enough to work 'live' or require a server restart. I'll attach what ive done for reference. -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-103) org.jboss.config.plugins.property.PropertyConfiguration

by Rashid Kamran (JIRA)

org.jboss.config.plugins.property.PropertyConfiguration ------------------------------------------------------- Key: JBMICROCONT-103 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-103 Project: JBoss MicroContainer Issue Type: Bug Components: Configurator Reporter: Rashid Kamran Priority: Minor PropertyConfiguration's constructor is not considering the check access before accessing system properties, this means at a bootstrap level by passing a null as parameter is equivalent to access the System.getProperties() without SecurityManager's involvement. -- 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, 11 months

2
2
0 / 0

[JBoss JIRA] Updated: (BPEL-186) Write a blog entry about the beta releases

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-186?page=all ] Alejandro Guizar updated BPEL-186: ---------------------------------- Fix Version/s: jBPM BPEL 1.1 beta 3 (was: jBPM BPEL 1.1 beta 2) > Write a blog entry about the beta releases > ------------------------------------------ > > Key: BPEL-186 > URL: http://jira.jboss.com/jira/browse/BPEL-186 > Project: JBoss jBPM BPEL > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documents > Reporter: Alejandro Guizar > Assigned To: Alejandro Guizar > Fix For: jBPM BPEL 1.1 beta 3 > > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Resolved: (BPEL-174) resume process execution after system restart

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-174?page=all ] Alejandro Guizar resolved BPEL-174. ----------------------------------- Resolution: Done jBPM BPEL now enables unfinished inbound message activities during initialization of the web app containing the process. If you want some fun, run the graphical ATM client and connect to the server. Undeploy the web app. Now deploy it again. Log on as ernie (or any other customer). The server will accept the operation as if nothing had happened. Point your browser to the URL pattern of the relation/integration servlet (e.g. http://localhost:8080/atm/relation). The partner integration console will show up. It provides a summary of the current pending receptions, the initial receptions, the outstanding requests (receptions which have not been replied) and partner service clients. > resume process execution after system restart > --------------------------------------------- > > Key: BPEL-174 > URL: http://jira.jboss.com/jira/browse/BPEL-174 > Project: JBoss jBPM BPEL > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Engine > Affects Versions: jBPM BPEL 1.0 alpha 4 > Reporter: Alejandro Guizar > Assigned To: Alejandro Guizar > Fix For: jBPM BPEL 1.1 beta 2 > > > Right now the relation servlet only opens message listeners for activities that create process instances. It must also load existing tokens pointing to inbound message activities and open their corresponding request listeners. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (BPEL-174) resume process execution after system restart

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-174?page=comments#action_12341672 ] Alejandro Guizar commented on BPEL-174: --------------------------------------- Fixed a small bug where findPickTokens returns a token positioned in an activity set to execute upon picking a message, because the parent of said activity is the pick. We are not looking for such a token. We want tokens positioned in begin marks. > resume process execution after system restart > --------------------------------------------- > > Key: BPEL-174 > URL: http://jira.jboss.com/jira/browse/BPEL-174 > Project: JBoss jBPM BPEL > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Engine > Affects Versions: jBPM BPEL 1.0 alpha 4 > Reporter: Alejandro Guizar > Assigned To: Alejandro Guizar > Fix For: jBPM BPEL 1.1 beta 2 > > > Right now the relation servlet only opens message listeners for activities that create process instances. It must also load existing tokens pointing to inbound message activities and open their corresponding request listeners. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3541) JDBCParameterSetter is not used for query parameters

by Alexey Loubyansky (JIRA)

JDBCParameterSetter is not used for query parameters ---------------------------------------------------- Key: JBAS-3541 URL: http://jira.jboss.com/jira/browse/JBAS-3541 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: CMP service Affects Versions: JBossAS-4.0.4.GA Reporter: Alexey Loubyansky Assigned To: Alexey Loubyansky Fix For: JBossAS-4.0.5.CR1 If JDBCParameterSetter is used for a type in type-mapping, it's not used to set parameters on the query. Currently, it's only used to set CMP field values on SQL statements. -- 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, 11 months

1
2
0 / 0

[JBoss JIRA] Commented: (BPEL-9) fault and termination handling

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-9?page=comments#action_12341670 ] Alejandro Guizar commented on BPEL-9: ------------------------------------- Fixed catch selection logic. > fault and termination handling > ------------------------------ > > Key: BPEL-9 > URL: http://jira.jboss.com/jira/browse/BPEL-9 > Project: JBoss jBPM BPEL > Issue Type: Sub-task > Components: Engine > Affects Versions: jBPM BPEL 1.0 alpha 4 > Reporter: Juan Cantu > Assigned To: Alejandro Guizar > Fix For: jBPM BPEL 1.1 beta 3 > > > -Implement the state transitions for scope instances when cancel or faulted signals are received > -Provide the fault catching logic -- 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, 11 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 August 2006