I have never run a testcase with XML, how would I do that?
The same way you'd run any other test case. Write java that does just as much of the process you're trying to test as necessary, without doing anything that might mess up your test.
In this case, I'd write a method that uses the API of ScheduleBuilder to parse the XML file. Even if I were using JUnit, I might not bother asserting anything about it -- sometimes it's enough to know that it didn't choke.
Then again, if the Quartz interface for a Schedule is reasonably open, it might not be hard to assert that the Schedule which was built has the right tasks, they have the right properties, etc. Remember that i know next to nothing about Quartz; that stuff was written by one of my colleagues who doesn't monitor the lists as carefully as I do.
I'll give you a hint: there's a test case in the jgs-quartz distribution that does essentially what you want. Get the source code and copy from it until you have what you need.
Joe
--- Thanks Mick Knutson
The world is a playground...Play Hard, Play Smart. Visit http://www.YourSoS.com to learn how our "Personal Emergency Alert & Contact System" can help you Play Smart.
+00 1 (877) SoS-9119 +00 1 (708) 570-2772 Fax ---
----- Original Message ----- From: "Joe Germuska" <[EMAIL PROTECTED]> To: "Struts Users Mailing List" <[EMAIL PROTECTED]> Sent: Friday, October 03, 2003 6:55 AM Subject: Re: Still an issue: Quartz plugin shutdown problem
set:At 19:26 -0700 10/2/03, Mick Knutson wrote: > >After even more toying, I get a different error about the job not being>(any thoughts here?)
Mick:
Have you tried writing a simple test case that runs your XML file through the JGSI Quartz SchedulerBuilder? You might be better off making sure that you can successfully parse the XML outside of your EJB container, instead of throwing it into the container for testing.
Also, it would help confirm or reject the possibility that it's something to do with the container -- since other people say they can parse it, that's probably the case, but if you have a test case, you can quickly validate changes you make to the XML external to the more complex deployment environment.
Joe
-- Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "We want beef in dessert if we can get it there." -- Betty Hogan, Director of New Product Development, National Cattlemen's Beef Association
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "We want beef in dessert if we can get it there."
-- Betty Hogan, Director of New Product Development, National Cattlemen's Beef Association
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
