om/map/* files are rendered twice

[Graham Leggett <mi...@sharp.fm>]

Hi all,

For some weird reason, when I run torque and get it to generate the 
files in the map directory, it generates the file twice in the same 
file, as attached. The resultant code does not compile.

Anyone have a fix or a workaround for this?

Regards,
Graham
-- 
-----------------------------------------
minfrin@sharp.fm		"There's a moon
					over Bourbon Street
						tonight..."

Re: om/map/* files are rendered twice

[Graham Leggett <mi...@sharp.fm>]

Graham Leggett wrote:

> For some weird reason, when I run torque and get it to generate the 
> files in the map directory, it generates the file twice in the same 
> file, as attached. The resultant code does not compile.

Found the problem - one of the tables had been defined twice. Can this 
not be improved to produce a sane error message?

Regards,
Graham
-- 
-----------------------------------------
minfrin@sharp.fm		"There's a moon
					over Bourbon Street
						tonight..."

Re: Testing with jUnit

[Jeff <je...@hotpop.com>]

    I've been able to use jUnit under the eclipse IDE to test my Torque 
projects.  One time I tried to use textui (so I could run the tests 
under a profiler) and couldn't.  I think it was the same problem. 


Malte Stien wrote:

>Hi,
>
>I wrote some jUnit test for my Torque project and they always fail if I test 
>them with the junit.swingui.TestRunner but they run fine if I use the 
>junit.textui.TestRunner. The tests also run fine if I disable the "Reload 
>classes every run"-checkbox in the swingui.
>
>I searched around a little and found that it has probably something to do with 
>the TestCaseClassLoader of jUnit. An article about that can be found in the 
>jUnit FAQ http://junit.sourceforge.net/doc/faq/faq.htm#running_8
>
>It says something about a list of classes that are not supposed to be loaded 
>by the class loader of jUnit. This list can be found in the junit.jar in the 
>file junit/runner/excluded.properties. The problem is though, that from my 
>perspective the list looks fine. It is supposed to contain classes that jUnit 
>does not have to reload every time. As far as I can see none of the Torque 
>classes match any of those patterns, do they?
>
>#
># The list of excluded package paths for the TestCaseClassLoader
>#
>excluded.0=sun.*
>excluded.1=com.sun.*
>excluded.2=org.omg.*
>excluded.3=javax.*
>excluded.4=sunw.*
>excluded.5=java.*
>excluded.6=org.w3c.dom.*
>excluded.7=org.xml.sax.*
>excluded.8=net.jini.*
>
>Did anybody use jUnit with Torque and knows how to configure that file if that 
>is really the problem?
>
>Thanks for help.
>Malte.
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
>For additional commands, e-mail: torque-user-help@db.apache.org
>
>
>  
>

Testing with jUnit

[Malte Stien <ma...@stien.de>]

Hi,

I wrote some jUnit test for my Torque project and they always fail if I test 
them with the junit.swingui.TestRunner but they run fine if I use the 
junit.textui.TestRunner. The tests also run fine if I disable the "Reload 
classes every run"-checkbox in the swingui.

I searched around a little and found that it has probably something to do with 
the TestCaseClassLoader of jUnit. An article about that can be found in the 
jUnit FAQ http://junit.sourceforge.net/doc/faq/faq.htm#running_8

It says something about a list of classes that are not supposed to be loaded 
by the class loader of jUnit. This list can be found in the junit.jar in the 
file junit/runner/excluded.properties. The problem is though, that from my 
perspective the list looks fine. It is supposed to contain classes that jUnit 
does not have to reload every time. As far as I can see none of the Torque 
classes match any of those patterns, do they?

#
# The list of excluded package paths for the TestCaseClassLoader
#
excluded.0=sun.*
excluded.1=com.sun.*
excluded.2=org.omg.*
excluded.3=javax.*
excluded.4=sunw.*
excluded.5=java.*
excluded.6=org.w3c.dom.*
excluded.7=org.xml.sax.*
excluded.8=net.jini.*

Did anybody use jUnit with Torque and knows how to configure that file if that 
is really the problem?

Thanks for help.
Malte.