ejb-jar.xml must either obey the right xml schema or define

[bjornbjorn]

When deploying, I get this error:

2006-05-12 14:20:23,093 DEBUG [org.jboss.deployment.scanner.URLDeploymentScanner] Failed to deploy: org.jboss.deployment.scanner.URLDeploymentScanner$DeployedURL@6e84099b{ url=file:/C:/Programfiler/jboss-4.0.4.CR2/server/default/deploy/ejb3-project.ear, deployedLastModified=1147436384531 }
org.jboss.deployment.DeploymentException: ejb-jar.xml must either obey the right xml schema or define a valid DOCTYPE!

This happens even if I use the example ejb-jar.xml I found here:
http://docs.jboss.org/ejb3/app-server/tutorial/jboss_resource_ref/META-INF/ejb-jar.xml

anyone know what the problem might be?

[bjornbjorn]

I still get this problem.

I do not get it if I specify:
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">

at the top - but that causes problems when deploying since it will try to validate the beans as 2.0 beans and not 3.0 beans.

Anyone?

[bjornbjorn]

Also, why doesn't the ejb-jar.xml from the EJB3 tutorial work? (http://docs.jboss.org/ejb3/app-server/reference/build/reference/en/html/partial_deployment_descriptors.html#d0e656)

Does it mean something is wrong with my server, or is it the tutorial which has an old ejb-jar.xml?

[bitl]

Start your file with:

<?xml version="1.0"?>
<ejb-jar version="3.0" xmlns="http://java.sun.com/xml/ns/j2ee">

I have concluded the solution reading this:
http://www.theserverside.com/discussions/thread.tss?thread_id=38282

At least it helped me to resolve your (and my) issue under jboss-4.0.4.GA.

[smajima]

"bitl" wrote:
Start your file with:

<?xml version="1.0"?>
<ejb-jar version="3.0" xmlns="http://java.sun.com/xml/ns/j2ee">

I have concluded the solution reading this:
http://www.theserverside.com/discussions/thread.tss?thread_id=38282

At least it helped me to resolve your (and my) issue under jboss-4.0.4.GA.

I tried this one. But there is still an error.

org.jboss.deployment.DeploymentException: expected one enterprise-beans tag
at org.jboss.metadata.MetaData.getUniqueChild(MetaData.java:113)
.......

Does anyone solve this problem?

[smajima]

I installed Jboss-4.0.4.GA-Patch1-Installer.jar.
And I checked by Jboss-Seam examples. They worked.

[digua]

It's strange because I intalled the same software and I deployed same project, but I got the error message.

[nadiaismail]

I get the same problem too .. did anyone manage to solve it?

[nadiaismail]

I had the same problem, and I realised that I had install JBoss All, instead of JBoss EJBProfile. Its resolved now with no changed necessary to the seam examples...

[timaar]

Tried changing the ejb file:

<?xml version="1.0"?>
<ejb-jar version="3.0" xmlns="http://java.sun.com/xml/ns/j2ee">

No succes it now gives:

expected one enterprise-beans tag

I don't have a line break in between as suggested in:

http://www.theserverside.com/discussions/thread.tss?thread_id=38282

I changed my jboss server with the patch version as provided in solution:

Jboss-4.0.4.GA-Patch1-Installer.jar
http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=16942

Anyone has other suggestion I really want to try this out but if the examples doesn't even work. I think that this is really a BETA! Not for testing yet...
:s

[timaar]

A question that I have and that might cause this issue is that in the Seam tutorial (http://docs.jboss.com/seam/1.0.0.GA/reference/en/html/tutorial.html#d0e198).

It states:

...
Next, make sure you set the location of your Tomcat 5.5 installation in the build.properties file in the root folder of your Seam installation.
...

My question now is: Do you have to install Tomcat seperate? Because the JBoss uses tomcat (it is build in I guess).

If we want to use the built-in tomcat of JBoss AS to what directory should we point it?

[timaar]

See

http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3951061#3951061

[vashistvishal]

Okiee,

I encountered this beast today as i was trying to get some hand on SEAM after i heard lots of good reviews. As mentioned in one of the posts here I 're-installed JBoss', using JEMS installer, using ption 'ejb3' on installer menu, previously i opted for option 'ALL'.

And when i deployed example of 'booking' from SEAM it deployed sucessfully.

Prior to this i had the above mentioned errors and i tried changing ejb-jar file as suggested above, but all those things didn't work.

So if you reinstall JBoss using ejb3 option than it will be fine, it is also metoined on JBoss app server download page specifically.
http://labs.jboss.com/portal/jbossas/download

I hope this helps, sometimes trying to become smart can bite you badly, as i encountered :)

Vishal

[r.marinho.gomes]

Hey Galera!!!

Try this:

<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd"
version="3.0">
...

--
Ricardo Marinho Gomes
[e-mail]

[klsateesh]

HI All,

I am getting the same error..

Insatlled JBoss-4.0.4GA and selected the ALL Option
and the SEAM Version i am using is jboss-seam-1.0.1.GA

When i don't use the below lines

<?xml version="1.0"?>
<ejb-jar version="3.0" xmlns="http://java.sun.com/xml/ns/j2ee">

i am getting the error

8907jboss-seam-registration.ear-contents/jboss-seam-registration.jar
org.jboss.deployment.DeploymentException: ejb-jar.xml must either obey the right xml schema or define a valid DOCTYPE!
 at org.jboss.metadata.ApplicationMetaData.importEjbJarXml(ApplicationMetaData.java:339)
 at org.jboss.metadata.XmlFileLoader.load(XmlFileLoader.java:166)

and when i use the above i am getting the Error

8911jboss-seam-registration.ear-contents/jboss-seam-registration.jar
org.jboss.deployment.DeploymentException: expected one enterprise-beans tag
 at org.jboss.metadata.MetaData.getUniqueChild(MetaData.java:113)
 at org.jboss.metadata.ApplicationMetaData.importEjbJarXml(ApplicationMetaData.java:371)
 at org.jboss.metadata.XmlFileLoader.load(XmlFileLoader.java:166)
 at org.jboss.ejb.EJBDeployer.create(EJBDeployer.java:541)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
 at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
 at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
 at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
 at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
 at org.jboss.ws.server.WebServiceDeployer.create(WebServiceDeployer.java:99)

Has any one solved this one yet !!

Thanks
Sateesh