A few days ago someone on the Mach-II mailing list posted about using the existing Mach-II DTD within Eclipse/CFEclipse to get code hints within the XML config file.
A few suggestions for XML editors came up (see end of this post for some links)… I remember doing this for Fusebox and as I’m now working with Mach-II thought I’d set it up again. I downloaded the free version of XMLBuddy and manually installed it into Eclipse. There is some confusion about using XMLBuddy in 3.2 but it works for me and I found a few other posts where people said they had no problems - YMMV.
Update: 2/11/2007:
Moved to my Wiki: CFEclipse, XMLBuddy and Mach-II DTD
You May Also Enjoy Reading:
8 Comments
I hate it when I’m an idiot! I’ve actually been trying to do this for a LONG time and had basically given up. Thanks for explaining this, I can’t believe how easy it is and have no idea how I missed it.
Brian - don’t feel bad. I’ve been working on my first Mach-II application for a few months now without it…
So far I’m finding it very useful- esp. in regards to closing tags which I always seem to forget!!
How would I adapt this for Fusebox. I get the association stuff with XMLBuddy but not the path name you’re putting in the DOCTYPE.
Can you help?
Check out this post by Nathan Strutz:
http://www.dopefly.com/techblo.....?entry=101
He’s using a different XML editor but it should be enough to get you going in the right direction.
Okay, that helped a bit but even Nathan says “I wish I knew what that all meant”.
It’s the path bit I don’t get. How do I tell the XML file, or CFEclipse, where I’ve put the DTD?
I need to sit down and play with this and figure out what exactly is required to make this work.
I dumped my .dtd file in with my mach-ii.xml file.
OK - digging around it looks like you can also reference the .dtd file with a full path (this assumes you are on Windows)
< !DOCTYPE mach-ii PUBLIC "-//Mach-II//DTD Mach-II Configuration 1.1.1//EN" "file:///d:/wwwroot/machii/mach-ii_1_1.dtd">
Thanks, that’s helped.