August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-495) Remoting 2.0.0.CR1 breaks existing org.jboss.remoting.security.SSLSocketBuilder deployments

by Ovidiu Feodorov (JIRA)

Remoting 2.0.0.CR1 breaks existing org.jboss.remoting.security.SSLSocketBuilder deployments ------------------------------------------------------------------------------------------- Key: JBMESSAGING-495 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-495 Project: JBoss Messaging Issue Type: Sub-task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Blocker Fix For: 1.0.1.CR4 -- 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_12340800 ] Alejandro Guizar commented on BPEL-174: --------------------------------------- Added reference to definition from ScopeInstance. Reenabled lazy loading for Nodes. Fixed overlapping problem between Scope.root and StructuredActivity.nodes associations. The Activity.compositeActivity association cannot be shared as the inverse of the two associations mentioned earlier. Fixed column name overlap in Alarm: CreateTimerAction already uses column REPEAT_. > 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: (JBMESSAGING-493) QueuedExecutor is bounded

by Tim Fox (JIRA)

QueuedExecutor is bounded ------------------------- Key: JBMESSAGING-493 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-493 Project: JBoss Messaging Issue Type: Bug Reporter: Tim Fox Assigned To: Tim Fox QueuedExecutors currentl are using a BoundedLinkedQueue which can get full and block -- 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
5
0 / 0

[JBoss JIRA] Resolved: (JBAS-3369) Add support for encrypting the tomcat server.xml keystore/truststore attributes

by Anil Saldhana (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3369?page=all ] Anil Saldhana resolved JBAS-3369. --------------------------------- Resolution: Done The functionality existed in JBoss for a long long time. We just did not have good documentation for this. Here: http://wiki.jboss.org/wiki/Wiki.jsp?page=EncryptKeystorePasswordInTomcatC... The SSLUnitTestCase has been retrofitted to test this. > Add support for encrypting the tomcat server.xml keystore/truststore attributes > ------------------------------------------------------------------------------- > > Key: JBAS-3369 > URL: http://jira.jboss.com/jira/browse/JBAS-3369 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service, Security > Affects Versions: JBossAS-4.0.4.GA > Reporter: Scott M Stark > Assigned To: Anil Saldhana > Priority: Critical > Fix For: JBossAS-4.0.5.CR1 > > > We have the ability to encrypt passwords in datasource/login-confg.xml files, but the tomcat server.xml parsing does not currently support this. This is something we need to add. -- 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] Updated: (JBAS-3369) Add support for encrypting the tomcat server.xml keystore/truststore attributes

by Anil Saldhana (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3369?page=all ] Anil Saldhana updated JBAS-3369: -------------------------------- Fix Version/s: JBossAS-5.0.0.Beta > Add support for encrypting the tomcat server.xml keystore/truststore attributes > ------------------------------------------------------------------------------- > > Key: JBAS-3369 > URL: http://jira.jboss.com/jira/browse/JBAS-3369 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service, Security > Affects Versions: JBossAS-4.0.4.GA > Reporter: Scott M Stark > Assigned To: Anil Saldhana > Priority: Critical > Fix For: JBossAS-5.0.0.Beta, JBossAS-4.0.5.CR1 > > > We have the ability to encrypt passwords in datasource/login-confg.xml files, but the tomcat server.xml parsing does not currently support this. This is something we need to add. -- 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: (JBESB-47) Migrate to EJB3

by Kurt Stam (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-47?page=all ] Kurt Stam resolved JBESB-47. ---------------------------- Resolution: Done Support is added. > Migrate to EJB3 > --------------- > > Key: JBESB-47 > URL: http://jira.jboss.com/jira/browse/JBESB-47 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: ESB Core > Reporter: Mark Little > Assigned To: Kurt Stam > Fix For: 4.0 Beta 1 > > > Currently Rosetta uses EJBs. We should look to move this to EJB3 support. One question though: since we can run EJBs outside of the application server, it may be worth looking at whether we use that facility, rather than tying the ESB to requiring an application server: ultimately we don't want that limitation, so it's worth looking at it from the outset. -- 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: (JBESB-106) remove the ESB part from the ESBConnectionException

by Kurt Stam (JIRA)

remove the ESB part from the ESBConnectionException --------------------------------------------------- Key: JBESB-106 URL: http://jira.jboss.com/jira/browse/JBESB-106 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 Beta 1 Reporter: Kurt Stam Assigned To: Mohit Keswani Priority: Minor Fix For: 4.0 Beta 1 remove the ESB part from the ESBConnectionException (It's already in an esb package) -- 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
1
0 / 0

[JBoss JIRA] Created: (JBAS-3446) Upgrade JBossSerialization to 1.0.2.GA

by Clebert Suconic (JIRA)

Upgrade JBossSerialization to 1.0.2.GA -------------------------------------- Key: JBAS-3446 URL: http://jira.jboss.com/jira/browse/JBAS-3446 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.4.GA Reporter: Clebert Suconic Assigned To: Clebert Suconic Fix For: JBossAS-5.0.0.Beta, JBossAS-4.0.5.CR1 -- 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] Commented: (JBIDE-322) Unused plugin dependency in org.jboss.ide.eclipse.ejb3.wizards.ui on org.eclipse.jdt.source

by Marshall Culpepper (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-322?page=comments#action_12340783 ] Marshall Culpepper commented on JBIDE-322: ------------------------------------------ Must've missed this ... i have removed the jdt.source dependency in the ejb3 feature and committed it into CVS. It will make our beta build this week. > Unused plugin dependency in org.jboss.ide.eclipse.ejb3.wizards.ui on org.eclipse.jdt.source > -------------------------------------------------------------------------------------------- > > Key: JBIDE-322 > URL: http://jira.jboss.com/jira/browse/JBIDE-322 > Project: JBoss IDE > Issue Type: Bug > Components: EJB3 plugin > Affects Versions: 1.5 Final > Reporter: Francois Granade > Assigned To: Marshall Culpepper > Priority: Minor > Fix For: 2.0.0.Alpha > > > The plugin org.jboss.ide.eclipse.ejb3.wizards.ui declare a dependency on org.eclipse.jdt.source. You can see that in the Manifest file: > http://fisheye.labs.jboss.com/viewrep/JBoss/jbosside/ejb3/plugins/org.jbo... > Unless I'm mistaken, this dependency is not needed (why would the wizard have a dependency on JDT source code ???) > It's innocuous, but this causes an error to appear in Eclipse error log. > Also, for us at http://www.easyeclipse.org, it means that we have to patch the manifest when we build it. It's small, but useless -- 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: (JBPM-443) JPBM does not work with MySQL 5.0

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-443?page=comments#action_12340772 ] Ronald van Kuijk commented on JBPM-443: --------------------------------------- Could the following statement throw a light on what is observered: - exception when inserting new boolean values - always returning false for bit values already in database Especially I'm curious to the exceptions... are they logged somewhere? > JPBM does not work with MySQL 5.0 > --------------------------------- > > Key: JBPM-443 > URL: http://jira.jboss.com/jira/browse/JBPM-443 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.0, jBPM 3.1, jBPM 3.0.1, jBPM 3.0.2, jBPM 3.0.3, jBPM 3.2 alpha 1, jBPM 3.1.1, jBPM 3.1.2, jBPM 3.0.4 > Environment: Windows XP, Mysql 5.0 beta2, JBPM 3.0 > Reporter: Ravi Prakash Reddy Ummadi > Assigned To: Tom Baeyens > > When JBPM is used with MySQL 5.0, the process is skipping the intermediate steps in the process definition. > The behaviour is unpredictable. The same works fine with MySQL 4.1 and other databases. > The problem may be in DB scripts ( DB scrips run fine though) or .hbm.xml files . -- 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