works like a breeze for me :). Here is what i did: - Disconnected the network - I had a single EJB wrapped up in a jar and deployed it to the apps folder, - started the server - view the log file which showed that it had successfully deployed the ejb - wrote a test client, looked up the ejb and called a method on it
Everything worked fine, did not see any errors or anything in the log which mentions anything about downloading a schema or looking for a schema. Is that what I was supposed to do to test it? If this is what I was supposed to do then the files can be deleted and OPENEJB-555 can be closed. On 7/3/07, David Blevins <[EMAIL PROTECTED]> wrote:
On Jul 3, 2007, at 10:13 AM, Karan Malhi wrote: >> Still have to clear up the sun xsd issue as mentioned earlier. > I deleted the xsd files from openejb-jee scheme directory and rebuilt, > it worked fine. I also looked into the JaxbJavaee and we are using a > non-validating SAXParser in there. Also looks like all the java > objects for the xsd files are generated, is there any other xsd for > which we still need java objects. Wouldnt simply deleting these files > fix the issue? Is there a place where we are dynamically generating > this tree of java objects and using them? We can definitely delete the xsds and let that be that. I'm not sure running offline works as it seems some bit of parsing code is still trying to get the schemas from the internet. I haven't tried yet but the way to test would be to unplug your network cable then boot the server with an app in it. -David
-- Karan Singh Malhi
