Jene Jasper wrote:
Keith,
To get validation working correctly for an UnmarhalHandler, that
supports xsi:nil, I have created the attached
TestCaseBug1723Unmarshaller. The used classes are generated based on
the attached bug1723.xsd. The asserts and fails that don't work as
expected are commente
Done...It's
http://bugzilla.exolab.org/show_bug.cgi?id=1855
--- Werner Guttmann <[EMAIL PROTECTED]> wrote:
>
> Jon,
>
> can you please file a bug report at
> http://bugzilla.exolab.org, and I'll look into this
> issue tomorrow. Actually, I have not changed lazy
> loading for
> collections, bu
public void
testCastorUnmarshallerTopValidationTag_Element_OptionalMultipleNillableDateTag()
throws Exception {
for (int i = 0; i < 2; i++) {
boolean setRoot = (i == 1);
String xml = ""
+ "2005-01-16"
+
"2005-01-16
public void
testCastorUnmarshallerTopValidationTag_Element_RequiredMultipleDateTag()
throws Exception {
for (int i = 0; i < 2; i++) {
boolean setRoot = (i == 1);
String xml = ""
+ "2005-01-16"
+
"2005-01-16"
package nl.abz.bug.xsi.nillable;
import java.io.*;
import junit.framework.*;
import org.exolab.castor.xml.*;
import nl.abz.bug.xsi.nillable.castor.wrapper.*;
public class TestCaseBug1723Unmarshaller extends TestCase {
public void
testCastorUnmarshallerTopValidationTag_Element_RequiredDateTag()
public void
testCastorUnmarshallerTopValidationTag_Element_RequiredMultipleNillableDateTag()
throws Exception {
for (int i = 0; i < 2; i++) {
boolean setRoot = (i == 1);
String xml = ""
+ "2005-01-16"
+
"2005-01-16
public void
testCastorUnmarshallerTopValidationTag_Element_RequiredNillableDateTag()
throws Exception {
for (int i = 0; i < 2; i++) {
boolean setRoot = (i == 1);
String xml = ""
+ "2005-01-16"
+
"2005-01-16"
public void
testCastorUnmarshallerTopValidationTag_Element_OptionalMultipleDateTag()
throws Exception {
for (int i = 0; i < 2; i++) {
boolean setRoot = (i == 1);
String xml = ""
+ "2005-01-16"
+
"2005-01-16"
public void
testCastorUnmarshallerTopValidationTag_Element_OptionalDateTag() throws
Exception {
for (int i = 0; i < 2; i++) {
boolean setRoot = (i == 1);
String xml = ""
+ "2005-01-16"
+
"2005-01-16"
public void
testCastorUnmarshallerTopValidationTag_Element_OptionalNillableDateTag()
throws Exception {
for (int i = 0; i < 2; i++) {
boolean setRoot = (i == 1);
String xml = ""
+ "2005-01-16"
+
"2005-01-16"
public void
testCastorUnmarshallerTopValidationTag_Element_DirtyXSINilWithValueCombination()
throws Exception {
for (int i = 0; i < 2; i++) {
boolean setRoot = (i == 1);
String xml = ""
+ "2005-01-16"
+
"2005-01-16
"http://www.w3.org/2001/XMLSchema"
targetNamespace="http://abz.nl/schemas/castor/bug1723"
xmlns="http://abz.nl/schemas/castor/bug1723"
elementFormDefault="qualified"
attributeFormDefault="unqualified">
Keith,
To get validation working correctly for an UnmarhalHandler, that
supports xsi:nil, I have created the attached
TestCaseBug1723Unmarshaller. The used classes are generated based on the
attached bug1723.xsd. The asserts and fails that don't work as expected
are commented out. For some Vali
Jon,
can you please file a bug report at http://bugzilla.exolab.org, and I'll look
into this issue tomorrow. Actually, I have not changed lazy loading for
collections, but only introduced support for lazy loading for 1:1 relations.
But it looks to me like Castor is getting confused a bug about
14 matches
Mail list logo
