Peter,
>So my question still stands - do you have DTDs in the jars?
>
>does
>
>$ unzip -t /opt/apps/phoenix/lib/phoenix-client.jar | grep dtd
>
>produce
>
> testing: org/apache/avalon/phoenix/tools/blockinfo.dtd OK
> testing: org/apache/avalon/phoenix/tools/assembly.dtd OK
>
>?
>
Found.
>If so extract them and make sure the info files work using those DTDs. Open
>up them in a validating editor or use validation tools to check it.
>
XMLSpy barfs. It thinks there is something wrong with the DTD. I
followed its suggested changes in Phoenix CVS (not committed).
Before:
<!ELEMENT service EMPTY >
<!ATTLIST service name CDATA #REQUIRED >
<!ATTLIST service version CDATA >
---
<!ELEMENT service EMPTY>
<!ATTLIST service
name CDATA #REQUIRED
version CDATA #REQUIRED
>
( i.e. one more #required )
Now it has been rebuilt, everything works. Please advise.
>If that doesn't work then you may need to specify the encoding attribute in
>the <?xml directive or something?
>
I am not sure that is the problem. I could be wrong as DTDs are not an
area of expertese, but I think the service attlist makeover fixes it.
Regards,
- Paul H
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
