This one time, at band camp, Martin Fuchs said:
MF>On 14.09.2004 20:20:52 Bruce Snyder wrote:
MF>
MF>> ...
MF>> The cast to java.sql.Connection is explained above. Castor has
MF>> always had plans to connected to data sources other than relational
MF>> databases. By allowing this method call to r
On 14.09.2004 20:20:52 Bruce Snyder wrote:
> ...
> The cast to java.sql.Connection is explained above. Castor has
> always had plans to connected to data sources other than relational
> databases. By allowing this method call to return a java.lang.Object,
> we're allowing other types of connection
Christian,
You should be able to implement an org.exolab.castor.xml.IDResolver and
pass it off to the Unmarshaller. When the Unmarshaller encounters and ID
that it doesn't know how to resolve, it will ask the registered
IDResolver to handle the resolution.
--Keith
Christian Schuhegger wrote:
>
This one time, at band camp, Martin Fuchs said:
MF>while looking through in Castor's source code the following question
MF>hit me one more time: Why is it made so difficult to retrieve the
MF>underlying JDBC connections from Castor?
MF>
MF>Yes, I saw the warning "Only for internal / advanced use
Hello castors,
executing the testcases against oracle 9.0.1 with the CVS version of castor
I recognized the following:
1. The tag in oracle.xml is missing.
2. TC66 fails with the following message:
1) [castor.oracle.TC66] Size
junit.framework.AssertionFailedError: Calling size() on a non-scrolla
Hello,
while looking through in Castor's source code the following question
hit me one more time: Why is it made so difficult to retrieve the
underlying JDBC connections from Castor?
Yes, I saw the warning "Only for internal / advanced use !" in
DatabaseImplgetConnection().
But some applications
hello,
i would like to read via castor an xml document which is not "complete",
that is, most objects are in a database and only some objects are in the
xml document and reference the objects in the database via their object ids.
i do not expect that this kind of functionality is working out of
Just a fair warning, the tests wont compile under jdk 1.5 First is that
the enum var name used everywhere is now a reserved word in 1.5, and
other issues in the source itself fail. I think all these issues revolve
around the use of 'enum' as a var name.
-Nick
The information contained in this me
Hello all, I am trying to run the jdo tests and have run into a silly
snag. For some reason the mapping file/class combo for the TestNested
stuff isn't working correctly. When I go to run the tests I get the
following stack trace on the outputs:
testsuite: castor
testsuite: mysql
Test: TC01 Duplic
Werner,
I have created another enhancement request 1739 for it. My internet
connection is slow so its taking time to download the full code.I will email
you as soon as I attach a patch to it.
Thanks
Kalpesh
-Original Message-
From: Werner Guttmann [mailto:[EMAIL PROTECTED]
Sent: Tuesday
10 matches
Mail list logo