July 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3982) HASingletonController emits a cluster-wide JMX Notification after starting/stopping singleton

by Brian Stansberry (JIRA)

HASingletonController emits a cluster-wide JMX Notification after starting/stopping singleton --------------------------------------------------------------------------------------------- Key: JBAS-3982 URL: http://jira.jboss.com/jira/browse/JBAS-3982 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.1.CR1 Provide a mechanism for cluster-wide notifications when singleton services are started and stopped. In conjunction with this, a special BarrierController variant could be developed that monitors the cluster-wide notifications, allowing service dependencies on remote singletons. -- 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

14 years, 4 months

5
4
0 / 0

[JBoss JIRA] Created: (JBAS-4193) Validation requirement should come from the model factory

by Scott M Stark (JIRA)

Validation requirement should come from the model factory --------------------------------------------------------- Key: JBAS-4193 URL: http://jira.jboss.com/jira/browse/JBAS-4193 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment services, XML services Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossAS-5.0.0.Beta2 A regression relative to how we parse application.xml without validation jbossas4.2 and earlier is showing up in placeholder application.xml deployments like: <!DOCTYPE application PUBLIC "-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN" "http://java.sun.com/dtd/application_1_3.dtd"> <application> <display-name>Resource Loading Ear</display-name> </application> This fails because this dtd requires at least one module as well: Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: vfsfil e:/C:/home/svn/JBossHead/jboss-head/testsuite/output/lib/unpacked/loadingresourc e2.ear/META-INF/application.xml@7,15 at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBPars er.java:173) at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java :180) at org.jboss.deployers.plugins.deployers.helpers.ObjectModelFactoryDeplo yer.parse(ObjectModelFactoryDeployer.java:83) ... 70 more Caused by: org.xml.sax.SAXException: The content of element type "application" i s incomplete, it must match "(icon?,display-name,description?,module+,security-r ole*)". @ vfsfile:/C:/home/svn/JBossHead/jboss-head/testsuite/output/lib/unpacke d/loadingresource2.ear/META-INF/application.xml[7,15] at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler .error(SaxJBossXBParser.java:406) at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(Unknown S To allow for similar behavior, we need to allow the ObjectModelFactory used by the deployer to indicate whether validation is needed. -- 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

14 years, 4 months

4
13
0 / 0

[JBoss JIRA] Created: (JBAS-4335) Verify whether -Djava.net.preferIPv4Stack=true should be disabled on Linux/jdk6+

by Dimitris Andreadis (JIRA)

Verify whether -Djava.net.preferIPv4Stack=true should be disabled on Linux/jdk6+ -------------------------------------------------------------------------------- Key: JBAS-4335 URL: http://jira.jboss.com/jira/browse/JBAS-4335 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: System service Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: JBossAS-5.0.1.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

14 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4197) Allow more control over hot deployment triggers

by Scott M Stark (JIRA)

Allow more control over hot deployment triggers ----------------------------------------------- Key: JBAS-4197 URL: http://jira.jboss.com/jira/browse/JBAS-4197 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Deployment services Reporter: Scott M Stark Assigned To: Dimitris Andreadis Fix For: JBossAS-5.0.0.Beta3 We need finer grained control over how hot deployment events are triggered. Two examples are: 1. Enable/disable the current hot deployment scanning based on time stamp for individual deployments 2. Allow a trigger hot deployment on next request mode. -- 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

14 years, 4 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-3633) Tidyup logging when transaction is no longer active

by Adrian Brock (JIRA)

Tidyup logging when transaction is no longer active --------------------------------------------------- Key: JBAS-3633 URL: http://jira.jboss.com/jira/browse/JBAS-3633 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JB5-Transaction Manager Affects Versions: JBossAS-4.0.5.CR1 Reporter: Adrian Brock Priority: Minor Since JBossTM rollsback transactions at transaction timeout, we need to tidyup the transaction demarcation code (commit/rollback/setRollbackOnly, etc) such that the logging is more information and not so noisy. We still need to communicate that the transaction rolled back even if it is not the transaction demarcation point that does the rollback. Currrently, you get errors/warnings about not being able to setRollbackOnly or rollback, because the transaction is already ended. -- 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

14 years, 4 months

4
4
0 / 0

[JBoss JIRA] Created: (JBAS-4070) Generalize naming factory and remoting lookup

by Scott M Stark (JIRA)

Generalize naming factory and remoting lookup --------------------------------------------- Key: JBAS-4070 URL: http://jira.jboss.com/jira/browse/JBAS-4070 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Scott M Stark Fix For: JBossAS-5.0.0.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

14 years, 4 months

3
7
0 / 0

[JBoss JIRA] Created: (JGRP-278) Externalization of socket creation in TCP/TCP_NIO (BasicTCP)

by Bela Ban (JIRA)

Externalization of socket creation in TCP/TCP_NIO (BasicTCP) ------------------------------------------------------------ Key: JGRP-278 URL: http://jira.jboss.com/jira/browse/JGRP-278 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.6 User configures a socket factory which creates client and server sockets. There is always 1 default factory configured. This allows developers to override socket creation, e.g. for use with SSL sockets. This way, TCP and TCP_NIO can be used with SSL. -- 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

14 years, 4 months

3
11
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-129) Implement support for the generic metadata in the javassist implementation of ClassInfo

by Adrian Brock (JIRA)

Implement support for the generic metadata in the javassist implementation of ClassInfo --------------------------------------------------------------------------------------- Key: JBMICROCONT-129 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-129 Project: JBoss MicroContainer Issue Type: Task Components: BeanInfo Affects Versions: JBossMC_2_0_0 Beta Reporter: Adrian Brock The support for generics has only been implemented in the reflection based ClassInfo implementation. This needs doing also for the Javassist implementation. -- 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

14 years, 5 months

6
9
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1392) WSRP does not submit the from when enctype set to "multipart/form-data"

by Andrey Adamovich (JIRA)

WSRP does not submit the from when enctype set to "multipart/form-data" ----------------------------------------------------------------------- Key: JBPORTAL-1392 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1392 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.CR2 Environment: All Reporter: Andrey Adamovich Assigned To: Chris Laprun We are developing a portlet on BEA WebLogic Portal that is supposed to be consumed later by JBoss Portal. This portlet is used for file data upload. The thing is that portlet contains a form that has enctype attribute set to multipart/form-data to enable file sending. When the form is submitted on the consumer (JBoss) no form parameters are passed to producer. Looking in the WSRP request sent to BEA Portal by JBoss only action name is seen. If enctype attribute is removed from the form then when form is submitted all parameters are sent to producer except file content. -- 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

14 years, 5 months

3
6
0 / 0

[JBoss JIRA] Created: (JBRULES-535) allow for plugeable query result handlers

by Mark Proctor (JIRA)

allow for plugeable query result handlers ------------------------------------------- Key: JBRULES-535 URL: http://jira.jboss.com/jira/browse/JBRULES-535 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: All Reporter: Mark Proctor Assigned To: Mark Proctor Fix For: 3.1-m1 Queries should be able to specify how the results are processed once they reach the terminal node. -- 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

14 years, 5 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2007