Bugs item #556816, was opened at 2002-05-16 08:26
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=556816&group_id=22866
Category: None
Group: v2.4 (stable)
>Status: Closed
>Resolution: Rejected
Priority: 5
Submitted By: Carsten Roettgers (pgnightshift)
>Assigned to: Scott M Stark (starksm)
Summary: empty <configuration-name> causes error
Initial Comment:
In JBoss 2.4.5 and 2.4.6 an empty <configuration-
name> tag in jboss.xml causes the following error:
[...]
[ERROR,XmlFileLoader] failed to load jboss.xml.
There could be a syntax error.
org.jboss.deployment.DeploymentException: Error in
jboss.xml for Bean BenutzerBean: configuration '' not
found in standardjboss.xml or jboss.xml
at
org.jboss.metadata.ApplicationMetaData.importJbossXml
(ApplicationMetaData.java:468)
at org.jboss.metadata.XmlFileLoader.load
(XmlFileLoader.java:186)
at org.jboss.ejb.ContainerFactory.deploy
(ContainerFactory.java:423)
at org.jboss.ejb.ContainerFactory.deploy
(ContainerFactory.java:370)
at org.jboss.ejb.ContainerFactory.deploy
(ContainerFactory.java:307)
at java.lang.reflect.Method.invoke(Native
Method)
at
com.sun.management.jmx.MBeanServerImpl.invoke
(MBeanServerImpl.java:1628)
at
com.sun.management.jmx.MBeanServerImpl.invoke
(MBeanServerImpl.java:1523)
at
org.jboss.deployment.J2eeDeployer.startModules
(J2eeDeployer.java:487)
at
org.jboss.deployment.J2eeDeployer.startApplication
(J2eeDeployer.java:459)
at org.jboss.deployment.J2eeDeployer.deploy
(J2eeDeployer.java:190)
at java.lang.reflect.Method.invoke(Native
Method)
at
com.sun.management.jmx.MBeanServerImpl.invoke
(MBeanServerImpl.java:1628)
at
com.sun.management.jmx.MBeanServerImpl.invoke
(MBeanServerImpl.java:1523)
at org.jboss.deployment.AutoDeployer.deploy
(AutoDeployer.java:395)
at org.jboss.deployment.AutoDeployer.run
(AutoDeployer.java:233)
at
org.jboss.deployment.AutoDeployer.startService
(AutoDeployer.java:371)
at org.jboss.util.ServiceMBeanSupport.start
(ServiceMBeanSupport.java:103)
at java.lang.reflect.Method.invoke(Native
Method)
at
com.sun.management.jmx.MBeanServerImpl.invoke
(MBeanServerImpl.java:1628)
at
com.sun.management.jmx.MBeanServerImpl.invoke
(MBeanServerImpl.java:1523)
at
org.jboss.configuration.ConfigurationService$ServicePr
oxy.invoke(ConfigurationService.java:967)
at $Proxy0.start(Unknown Source)
at org.jboss.util.ServiceControl.start
(ServiceControl.java:79)
at java.lang.reflect.Method.invoke(Native
Method)
at
com.sun.management.jmx.MBeanServerImpl.invoke
(MBeanServerImpl.java:1628)
at
com.sun.management.jmx.MBeanServerImpl.invoke
(MBeanServerImpl.java:1523)
at org.jboss.Main.<init>(Main.java:208)
at org.jboss.Main$1.run(Main.java:110)
at java.security.AccessController.doPrivileged
(Native Method)
at org.jboss.Main.main(Main.java:106)
[...]
JBoss 2.4.4 accepted empty <configuration-names> as
in the following excerpt from jboss.xml:
[...]
<enterprise-beans>
<entity>
<ejb-name>BenutzerBean</ejb-name>
<jndi-name>BenutzerBean</jndi-name>
<configuration-name></configuration-name>
</entity>
[...]
----------------------------------------------------------------------
>Comment By: Scott M Stark (starksm)
Date: 2002-05-16 08:41
Message:
Logged In: YES
user_id=175228
This is the correct behavior as the previous versions were
not validating this element correctly. Only absense of the
configuration-name implies the default configuration for
the bean type.
----------------------------------------------------------------------
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=556816&group_id=22866
_______________________________________________________________
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
