Search found 7 matches

by cberrymd
Tue May 16, 2006 5:20 pm
Forum: XML Schemas
Topic: Xforms validation
Replies: 5
Views: 13453

Brilliant. All fixed.
by cberrymd
Mon May 15, 2006 10:59 pm
Forum: XML Schemas
Topic: Xforms validation
Replies: 5
Views: 13453

Xforms validation

I have created two Xform files that are identical except for the <html ...> tag. This one followed the advice I found on this forum. It validates, but will not run. <?xml version="1.0" ?> <html xmlns= "http://www.w3.org/2002/06/xhtml2/" xmlns:xf= "http://www.w3.org/2002/xfor...
by cberrymd
Wed Feb 01, 2006 10:58 pm
Forum: XML Schemas
Topic: Correct use of xsd:duration
Replies: 1
Views: 7466

Correct use of xsd:duration

I have an element named dateEntered. To be valid it must be within the past 2 weeks. This explains what I'm trying to get to in pseudocode. attribute dateEntered { xsd:date { minInclusive ="today" - P14D maxInclusive ="today" } } , # a date within the past two weeks Can somebody ...
by cberrymd
Thu Jan 26, 2006 12:48 am
Forum: Common Problems
Topic: FATAL ERROR - can't find Java Virtual Machine on 7.0
Replies: 24
Views: 14869

That fixed it. Thanks!
by cberrymd
Fri Jan 20, 2006 9:31 pm
Forum: Common Problems
Topic: FATAL ERROR - can't find Java Virtual Machine on 7.0
Replies: 24
Views: 14869

I have both ibm and Sun. How can I tell <oXygen/> where to find the Sun version it wants?
by cberrymd
Wed Jan 18, 2006 7:43 pm
Forum: Common Problems
Topic: FATAL ERROR - can't find Java Virtual Machine on 7.0
Replies: 24
Views: 14869

No. That is when I get the error message. After I ignore it <oXygen/> starts, but I don't expect that the JRE scripts will run properly.
by cberrymd
Wed Jan 18, 2006 1:04 am
Forum: Common Problems
Topic: FATAL ERROR - can't find Java Virtual Machine on 7.0
Replies: 24
Views: 14869

FATAL ERROR - can't find Java Virtual Machine on 7.0

I'm running Redhat EL4 and have been using <oXygen/> 6.x without problems. Updated to 7.0 and I get: "FATAL ERROR <oXygen/> requires a Java Virtual Machine..." My java version is 1.4.2 which shouldn't be too old. What gives? What's really weird is that this is not a very fatal FATAL ERROR ...