Gary Marsh wrote :
| Do I need to update an .xsd file somewhere?
|
There is no .xsd file.
The schema is in-memory generated from metadata classes.
e.g. see AbstractBeanMetaData from MC and JBossXB project
My guess would be you're missing
MC's classloading and aop-mc-int on the classpath,
Thanks for the reply alesj;
I tweeked the classpath to include all of the MC's library jars and it compiles
and parses past the previous error. Now I am getting the following runtime
error:
JBoss-MC-Demo DEBUG [07-01-2009 08:52:59] JBossEntityResolver - Cannot resolve
alesj; Just a Note: when I substitute the JBossAS library Jars for the MC
Library jars in my classpath the error goes away. I last updated my MC 2.0.2GA
download 12/04/08.
Regards,
GMarsh
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4200145#4200145
Reply
Gary Marsh wrote :
| Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source:
Failed to resolve schema nsURI=urn:jboss:spring-beans:2.0 location=beans
|
This means you're missing MC's spring-int lib in classpath.
View the original post :
alesj; I spoke too soon regarding the clean run. I had a previously compiled
jar of my own in the classpath that apparently provided information needed to
resolve this error. When I removed it from the classpath the error returned.
Now I only have MC 2.0.2GA libraries in the path and I get
See my previous post.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4200188#4200188
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4200188
___
jboss-user mailing list
