RE: Could not locate compiled schema resource

[Radu Preotiuc-Pietro <ra...@bea.com>]

Well, it looks like the classloader ought to be able to find the new resources once you redeploy. Basically, we pretty much use ClassLoader.getResourceAsStream() to find .xsbs in the classloader, as you would expect, we don't have any control over what's available when. Your best bet is to check how are classloader built and managed in JBoss.

Radu

-----Original Message-----
From: Rob Harrington [mailto:robot252@yahoo.com]
Sent: Tuesday, March 29, 2005 12:12 PM
To: user@xmlbeans.apache.org
Subject: Could not locate compiled schema resource


I am having a very similar problem to the one which
started this thread.  Basically same exception,
indicating that the xsb resource is not found.  The
difference is that the resource the message says it is
looking for is definitely in the generated package. 
This happens when deploying the new package (built
from changes to an xsd file) as part of a war
deployment in jboss.  The generated package contains
only newly built files.

This may very well be a jboss issue or an issue with
the way I have jboss configured but I was hoping
someone on this list might have come across this issue
and hopefully solved it.  Note: restarting jboss
appserver solves the problem, but that's obviously not
ideal.

More details upon request.

Thanks.


		
__________________________________ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/ 

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: user-help@xmlbeans.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: user-help@xmlbeans.apache.org