April 2008 - jboss-jira - Jboss List Archives

[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, 6 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, 6 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, 6 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-5128) JaasSecurityManagerService/AuthorizationManagerService need to retire

by Anil Saldhana (JIRA)

JaasSecurityManagerService/AuthorizationManagerService need to retire --------------------------------------------------------------------- Key: JBAS-5128 URL: http://jira.jboss.com/jira/browse/JBAS-5128 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: EJB3, Security Affects Versions: JBossAS-5.0.0.Beta3 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: JBossAS-5.0.0.CR1 Since we injecting Security Managers into the deployers via beans, there is no need for these JMX MBean Services. -- 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, 6 months

3
8
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, 6 months

4
4
0 / 0

[JBoss JIRA] Created: (JBAS-5309) Revisit Security Injection

by Adrian Brock (JIRA)

Revisit Security Injection -------------------------- Key: JBAS-5309 URL: http://jira.jboss.com/jira/browse/JBAS-5309 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Security Reporter: Adrian Brock Assigned To: Anil Saldhana Fix For: JBossAS-5.0.0.CR1 The way security injection and dependency is working is a mess. 1) Some bits are passed as attachments 2) The Tomcat deployment mechanism needs redoing anyway 3) There's no way to override some things per deployment 4) The service dependencies of the security implementation don't look well defined 5) There's no real way to depend upon a specific login module, you have to depend on the XMLLoginConfig -- 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, 6 months

4
7
0 / 0

[JBoss JIRA] Created: (JBAS-5235) Add a warning comment in the example datasource descriptors about local datasources

by Dimitris Andreadis (JIRA)

Add a warning comment in the example datasource descriptors about local datasources ----------------------------------------------------------------------------------- Key: JBAS-5235 URL: http://jira.jboss.com/jira/browse/JBAS-5235 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JB5-Transaction Manager Reporter: Dimitris Andreadis Assigned To: Jonathan Halliday Priority: Critical Fix For: JBossAS-5.0.0.CR1 Please, add your comments and re-assign it too me. I suppose the wiki needs updating too. -- 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, 6 months

5
13
0 / 0

[JBoss JIRA] Created: (JBAS-5471) Deploying EJB3 service throws "java.lang.RuntimeException: No MBeanServer has been injected"

by Galder Zamarreno (JIRA)

Deploying EJB3 service throws "java.lang.RuntimeException: No MBeanServer has been injected" -------------------------------------------------------------------------------------------- Key: JBAS-5471 URL: http://jira.jboss.com/jira/browse/JBAS-5471 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB3 Affects Versions: JBossAS-5.0.0.Beta4 Reporter: Galder Zamarreno Assigned To: Galder Zamarreno Fix For: JBossAS-5.0.0.CR1 I'm trying to deploy an EJB3 service but I'm unable to do so as the following is thrown: 2008-04-22 17:21:20,640 ERROR [STDERR] (main) Caused by: java.lang.RuntimeException: No MBeanServer has been injected 2008-04-22 17:21:20,641 ERROR [STDERR] (main) at org.jboss.ejb3.deployers.JBossASKernel.installMBean(JBossASKernel.java:135) 2008-04-22 17:21:20,641 ERROR [STDERR] (main) at org.jboss.ejb3.service.ServiceContainer.registerManagementInterface(ServiceContainer.java:587) Please find attached: - source code for EJB3 service - deployment archive - server.log with TRACE on org.jboss.ejb3 I suspect Ejb3JBoss5Deployment should be injecting mbeanServer in the kernelAbstraction but it doesn't: public Ejb3JBoss5Deployment(DeploymentUnit ejb3Unit, Kernel kernel, MBeanServer mbeanServer, org.jboss.deployers.structure.spi.DeploymentUnit jbossUnit, DeploymentScope deploymentScope, JBossMetaData metaData, PersistenceUnitsMetaData persistenceUnitsMetaData) { super(ejb3Unit, deploymentScope, metaData, persistenceUnitsMetaData); this.jbossUnit = jbossUnit; kernelAbstraction = new JBossASKernel(kernel); // todo maybe mbeanServer should be injected? this.mbeanServer = mbeanServer; } I'll have a go at passing the mbeanServer to the kernelAbstraction and see if that fixes 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

14 years, 6 months

4
12
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, 6 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, 6 months

3
11
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2008